Newbie Questions For ASP.NET 2.0 1

[TunaAdmiral]

Good afternoon!

I have just started playing with ASP.NET 2.0 in the last few days. While some of the features are very nice, I am incredibly confused by the complilation and deployment paradigm that is used in 2.0.

In 1.1, I was able to compile and distribute my entire web project in under a minute. That was because version 1.1 created a single .dll in the bin directory. Version 2.0 doesn't make ANY .dlls (at least ones that are readily visible to the human eye.) You can deploy your entire web solution using the "Publish Web Site' option of the VS2005 IDE, but this actually transfers every f@#$ing file in your project to the destination. You can't just send a single assembly and a .aspx page or two. I'm rambling like a madman now....

I feel very frustrated, and very stupid. Could someone explain to me how this works?

For example, lets say that I need to add comma to one of my code-behind files. How can I compile my project, and only send the files to the web server that need to be sent?????? WHERE ARE THE FILES THAT ARE COMPILED BY ASP.NET? I'd like to send them via a third-party FTP client if possible. The VS2005 IDE is way too clunky.

Any help would be appreciated.

Thanks!

Mad Man Mikey

 

[BoulderBum]

If you hate the new build process, welcome to the club. The new build methodology, by default, makes a .dll for each page which is randomly named and completely worthless if you want to deploy a small change without redeploying the whole site.

Instead of fighting with the new stuff, I ended up using a tool called "Web Deployment Projects" which you can find here:

http://msdn.microsoft.com/asp.net/reference/infrastructure/wdp/default.aspx

.

It will let you compile a single deployable .dll like in 1.x.

 

[TunaAdmiral]

Thank you, BoulderBum!

It's heartening to know I'm not alone in this.

Thanks for the link! At a glance it looks like just the thing.