When deploying a site, the previous version should continue to run. If the deployment fails, the site should continue to run on the previous version. If it succeeds, the switch should happen after publication is complete.

It would be helpful if they allowed you to add a html comment specialized in letting the designer know that a specific region is using a specific JavaScript file that represents the view model. That way when the designer can’t figure it out, we can override it to be very specific. This would be very similar to the design time XAML syntax you can use to tell it the data bind type.

Compiling views on the webserver takes a lot of ressource, and during that time the application is slow to respond.
I would be great if we could publish compiled versions of our views. I know razorgenerator do this, but it's not native and we only want compile views for deployment, not when developing.

Thanks

Right now when you have a 64 bit Web project in Visual Studio 2012 it will always launch the iis express 32 bit version. Can we make Visual studio smarter depending on the platform on what iis express to load. Or at least allow for us to change that path inside the csproj file?

asp.net membership database schema, change uniqueidentifier datatype of primary keys to int fo all tables.

Allow Web.Config transforms to be applied to a deployment package without a rebuild under a different configuration.
QA packages can then be converted to production release packages without fear of introducing any subsequent changes.
Add ins exist but would prefer to have built in support

It would be nice to enable generic declaration in the markup of an asp.net page and adapt framework to have generic controls. For example: <asp:ListView`1[SomeClass] runat="server" ... like it is done in settings file for .net application

HttpContext.AcceptWebSocketRequest() internally uses IIS7WorkerRequest, which makes high-level WebSockets support in ASP.NET depend on IIS. But IIS is not the only http.sys-based web server for ASP.NET! (http://ultidev.com/products/UWS/) To enable other ASP.NET web server vendors support for WebSockets, *HttpWorkerRequest should be modified to include WebSockets access virtual methods*, and HttpContext.AcceptWebSocketRequest() should call standard HttpWorkerRequest interface instead of proprietary IIS7WorkerRequest.

HttpWorkerRequest must have WebSockets interface used by

I hate the fact that after publishing an asp.net web app, I need to remote into the server and encrypt connection strings and perhaps other sections of my web.config. It would be great if I could automatically kick off a post-deployment script which would do this for me.

The behaviour of slidingExpiration prevents sliding expiration from being used to provide a precise time out. By default

"To prevent compromised performance, and to avoid multiple browser warnings for users who have cookie warnings turned on, the cookie is updated when more than half of the specified time has elapsed. This might cause a loss of precision. " - http://msdn.microsoft.com/en-us/library/1d3t3c61.aspx

It'd be great to be able to configure things so the cookie renews every time. Because this functionality isn't available, numerous people have built their own version of the renew the cookie every time sliding expiration behaviour.

Thanks

Code Outlining for Razor on Web Pages

like on html or c#, the colapse block of code (-) or expand (+).

Thanks,
Oscar Azevedo

StateContainer(ViewState)]

string FirstName
{
get;
set;
}

[StateContainer(Session)]
List<string> myList
{
get;set;
}

[StateContainer(Cache)]
List<string> myList2
{
get;set;
}

Just a random thought: I think it would be nice, with the help of an attribute, to be able to define where a given property would be stored.

I guess it also be applied at the class level, if you want all of your properties to inherti the same StateContainer Attribute.

A change probably best fit for an upcoming Framework release.

Just a thought.

Edit and Continue is only allowed with the casini web server which to be honest is really lacking. We try to develop in IIS and without this feature our productivity is lacking due to the recompiles which can take over several minutes due to the large solution we work with.

It would be really cool if the BundleResponse class was able to return binary content instead of just text content. This way it would be possible to create image bundles (sprites).

I like to unit test a lot of my code, but hate mocking HttpContextBase just do to the horror of using something like Moq. It would be great to have a part of ASP.Net that was dedicated to unit testing and had built it classes that made it super simple to create mocks without heavy setup in my tests.

Also just make everything virtual in ASP.Net so we can override any public behavior (maybe not as possible).

Currently there is a trend back to moving towards having static content being generated during a build process. It would be interesting if either by extension or by a plugin to be able to generate static content using the layout and views during a build.