VS 2005 Build vs Precompilation vs VS 2003 Build

VS 2005 Build vs Precompilation vs VS 2003 Build

Post by news.micro » Fri, 23 Dec 2005 00:29:10


I recently started working with VS 2005 Professional and still work with VS
2003 and recognizing that things have changed I have a few questions about
the build and publish features in VS 2005 vs the build function in VS2003. I
just can not wrap my head around how it would work in real life, so please
bear with me.

In VS 2003 when you do a build (ASP.NET) you get your code (behind) compiled
into a dll, and if you use additional projects which compile in a dll too,
they will be placed in your bin dir. The you could place the bin folder plus
your ASPX pages on a production server and you were done.

1) Am I correct in understanding that in VS2005 you publish your source code
on a production server as it will be dynamically compiled?

2) Is it still possible to get your dll, and place this plus your aspx pages
on the production server?

3) Am I correct in understanding that when you use the publish feature in
VS2005, it copies everything from your source directory to the production
server and overwrite everything what was there no matter what?

4) When you use the copy web site feature, the source directory is really
your source directory instead of the location where you had build the web

5) Am I correct in understanding that it is now acceptable to place your
source code on a production server?

Well, I guess you can see by now that I am totally confused, and I hope you
can find the time to show me the light. Don't get me wrong I love the new VS
IDE but I fail to understand how the compilation has changed.

Please let me know if you know some articles where these subjects are better
explained than in the books I have.



1. VS.2005 Build vs. Build Order in output window

2. JSP vs. Struts vs. JSF vs. Swing vs. Tapestry vs. Spring vs. Rails

I am a JSP developer and am constantly feeling like I am missing the
boat by not using any of the other frameworks out there.

However, the couple I have looked at (JSF and Rails) don't impress me.
In JSP, I keep all of my logic in Servlets/Beans and all of my
presentation in the JSP file, making custom tags when I need to do some
HTML that involves some logic. So Servlets and Tags are the glue to the
JSPs and Beans. I don't see what is wrong with this model. The
biggest advantage is its flexible.

An example of my frustation with JSF (which is different than all the
other complaints) was attempting to popup a JSF page in a new window, I
had to to some hokey stuff to make it happen. Rails seems to claim how
easy it is to get something up and running. Well, I don't mind taking
a day (or a week) to get my foundation right, and then having a
flexible, high performance base from which to develop from. I don't
want 80% to be easy and then the last 20% to be practically impossible.

And, finally, I am confused by all the other choices that I haven't
even mentioned. However, I'm not looking for a dozen replys that say
'Go try this or that'.

I would like to know: What is wrong with a JSP/Custom
Tags/Servlet/Beans design (Not necessarily the full J2EE model 2)?


3. references in web services project in VS 2005 vs. VS 2003

4. Access 2002 vs 2003 vs VS 2005?

5. VS 2003 Vs VS 2005 speed

6. A comparison of VS.NET 2003 vs. VS.NET 2005

7. Compare MCSD with VS 2003 vs VS 2005

8. A comparison of VS.NET 2003 vs. VS.NET 2005

9. VS 2005 vs VS 2003

10. VS 2003 vs VS 2005

11. VS6 vs. VS 2002 vs. VS 2003 - more questions

12. comparision Jini vs CORBA vs .NET remoting vs. DCOM vs. web services vs. Java RMI

13. Emacs vs GPS vs Eclipse, Ada vs Lisp vs Lua vs Java

14. Rake vs SCons vs Boost.Build v2 vs Perforce Jam