http://codeguru.com/net_general/Meditating.html
"Meditating Upon the ASP.NET Code-Behind Model "
" * The code-behind model is mandatory
* Visual Studio .NET compiles down to a single DLL and causes the application to restart when updates are deployed
* Lack of compile-on-demand features. It requires an explicit compile step to deploy and run
* Inability to open single .aspx page without a project file
* Missing support for direct (local) IIS access or FTP access to files
* IIS must be installed on the development machine and administrative privileges are required to edit files
* Debugging different scenarios is quite hard and moving projects to another machine can be a nightmare
"
It's a pretty good article.
And I can add some more problems in vs.net:
vs2k2 only work for dotnet1.0, you need pay more to get one work for 1.1, called vs2k3.
vs2k3 may be out of date very soon too, cause dotnet 2.0 is coming soon, get your money ready for that.
can not color coding code inline.
it's a bad html editor, comparing with dreamweaver.
it will add garbage tag in your aspx pages.
....