.NET Questions

I am right now precompiling whole site,and deploying on clients intranet.But,it is cumbersome.Since,even a small change means,compiling whole site,and redeploying.What better options are available?

I think you're wrong in your assumption.

An ASP.net 2.0 page, like JSP, is compiled the first time it is used.

So for a small change, eg one page, you simply upload the new page.

You don't *have* to pre-compile the whole thing, but if you want to for whatever reason take a look at Web Deployment Projects.

So how is everyone deploying their Asp 2.0 apps?  Using Web Deployment Project (complie code behind to one assembly), deploying all application files (aspx & cs files) or using the publishing feature in VS.Net?  I've used both Web Deployment project and x-copy (aspx & cs) files.

Step 1:
Publish web site. Settings checked are: allow updateable, fixed naming and single page assemblies.

Step 2:
Copy published site to build machine. The copy script also makes sure to not copy .FLA files (flash source code files) and .FLP (flash projects), as well as any .VB or .CS files that might get out somehow.

Step 3:
Using a build project, make it so!

note: we use the team server version of visual slow.

My goal by the end of the year is to have this all automated.

I think,I will like to go with single page assemblies.Any drawbacks with this?

We hated the new Web site model in 2.0 so much that we refused to use it. Per-page assemblies makes it a nightmare to refer successfully to control types in pages, which we tend to do a lot.

Our solution? Adopt the Web Application Project model (http://webproject.scottgu.com). It's the standard .NET 1.x Web application model, ported to 2.0. Much, much better. This is now an official add-on for VS2005, and will ship with SP1 (whenever that happens) and with VS2007. And it should have shipped in the box with VS2005 if Microsoft had had any sense. What were they thinking?

Thankfully, if you're using a source control system with auto-merging capabilities, you don't have the eternal 'who's got the project file checked out' problems that were the main reason Microsoft created the broken 2.0 Web site model in the first place.

Trust me. You'll thank yourself later :-)

+1 to above post.

Generally, you only need to upload your aspx and DLL files.