I posted a couple MSDN Feedback Center Suggestions today (after it finally appears to be working again)… If you think these make sense stop by and vote on them to get them to the attention of the powers that be. I don't expect them to make much of a difference at this point, but the first one at least I think is important enough to try for a last push...

Provide Fixed Names Compilation for ASP.NET 2.0 without Individual Page Compiles

http://lab.msdn.microsoft.com/productfeedback/viewfeedback.aspx?feedbackid=af139938-ae15-4cbd-953a-2b8a95a150e5

This relates to the pre-compiler issues I’ve been writing about. The issue is that the current pre-compiler does not provide any way to create repeatable compiler output currently unless you run with source code. All of the various compilation models end up either with unique assembly names or unique .compile files which means that you pretty much need to delete all files before redeploying an application regardless of how small the change is. I suggest that there be a way to create a repeatable compile so you don’t have to delete before re-deploying but you can copy ontop.

Why does that matter? It minimizes the downtime for a Web site – if you copy a few DLLs that are essentially unchanged you can probably update the application without taking down the app as the impact of the file copies will be minimal. With non-repeatable compiler output you end up with mismatches and in-place and running updates are a thing of the past (unless you don’t care about errors while updating).

SmartPhone .NET 2.0 Support without Magneto in Visual Studio .NET

http://lab.msdn.microsoft.com/productfeedback/viewfeedback.aspx?feedbackid=c93a5e0e-8a7e-4ed5-a4da-c9b0ea15139a 

Currently Visual Studio .NET can target SmartPhone (and Windows CE) for Version 1.0 as in VS.NET 2003 and for Windows Mobile 5.0 (Magneto) with .NET 2.0. However there’s no way to target .NET 2.0 on a non-Magneto phone. I believe you can run .NET 2.0 applications on non-Magneto phones however – it’s just that VS.NET 2005 is lacking support for it. It sure would be nice to use the SmartPhone .NET 2.0 framework with older phones, especially given that Magneto phones are non-existent in the market at the moment.