Simple membership isn't as simple as original membership, would rather depend on it

XslCompiledTransform doesn't fully function in partial trust environments because if the TrustedXslt enum is used at construction, and the file contains <msxml:script> blocks, then the script is compiled dynamically to the process identity's Temp directory (C:\Users\<app pool identity>\Local\Temp on most machines).
As it's compiled code, why not put it in the standard .NET Temporary Files directory, thus allowing it to function perfectly well in partial trust environments?

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?

Code Outlining for Razor on Web Pages

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

Thanks,
Oscar Azevedo

Why not use for *.ts the same mechanism used for compiling *.ascx and *.aspx to DLLs? There is a whole infrastructure of build providers that can be utilized for this purpose. If compilation of TypeScript sources get implemented as a build provider, it will work even without Visual Studio, with any editor.

Currently the <text> placeholder element assumes HTML content in Visual Studio formatting.
The addition of attributes (namely, "type" for Content-Type) to control Visual Studio's parser/formatter in these blocks would be quite useful for templating non-HTML content in template methods.

For example:

@{ object template = @<text type="text/css">
.foo { background-image: url("foo.png"); }
.bar { background-image: url("bar.png"); }
</text>; }

The type attribute in this case would enforce formatting of the template contents as CSS.

I find that if I include pre-minified files into my bundle I run into lots of errors on the front-end, where if I just took said minified script and included it manually in the head, it works fine.

I'd like to be able to tell the bundler "Chillax, this dude has already been compiled"

Bundling is a cool idea, but it doesn't always play nicely with the ScriptManager when used in a webforms scenario. I would like to propose the ability to set a flag on the ScriptManager that would allow it to minify the combined scripts its serving.

It would be great if you had a gallery of websites built using MVC so people could see the power of this great tool.

Data Annotations are amazing in MVC models and really help with jquery unobtrusive. It would be great it they enhanced them so you had more than just Required or Regular Expressions. RequiredIf would help have conditional requirements for complex forms.

ConfigurationManager (and/or WebConfigurationManager) could have a really cool dynamics implementation, whereby they returned singleton instances when doing something like WebConfigurationManager.ConnectionStrings.LocalSqlServer, which could return a type-specific instance of a SqlClient connection to my given connection string.

In Webforms on Visual Studio 2010, you could update a code file even while the server was running - or you could stop the server, update code and the updates push through although the server is stopped.

In MVC, you can only update a view but not a controller while the server is running. Maybe i dont understand the inner workings but it sure made quick development updates faster without having to 'start debugging'

The ability to do Russian Doll Caching like you can in Rails.

It would be better to show some JavaScript syntax error(possibly compiling/parsing JavaScript code referred in the page) while we build our application using Visual Studio. We could correct these at compile time rather than finding at run time.

In the HTML editor, Intellisense suggests close tags are in alphabetical order rather than the tag close order.
e.g. If I type <article><header><span>, the suggested close tags are </artcle></header></span> rather than </span></header></article>.

Support of DBGeography is limited to EF. I tryed to use SQLDatasource and some of classic ASP.NET Webform Data controls and it seems that asp.Parameter have no fitting type. Also direct casting in inserting Event doesnt work. As I have seen also on other places there is *no* Support for the datatype which have been introduced with SQL 2008. As example sql2linq.
The point is, to prevent a complete new implementation only for reason to add one db field