Please provide a new project type in Visual Studio for developing JavaScript components.

The new project type could have the following features:

- Contains .js, .css, and .html files.
- Represents a complete UI component - i.e. a module or widget.
- Runs JSLint or JSHint on build and reports any errors and violations.
- The build ouput is minified JavaScript and CSS; there should be options for specifying a minifier.
- The build output should also output any HTML files (as ASP.Net partial views).
- The new project type permits adding references to other JavaScript projects.
- Intellisense is provided based on the referenced projects.
- ASP.Net MVC projects should also permit referencing of these new JavaScript projects.
- ASP.Net MVC should provide razor @Script/@Style syntax to include the minified bundles with reference to their project names.
- ASP.Net MVC should permit referencing the partial views from the build output.
- Similarly a JavaScript test project should also be provided; this project type permits referencing the new JavaScript projects.
- Test methods in the test projects are picked up and displayed in the Test Runner - the same as any C# test method.
- The test projects include a built-in assertion library, or permit external libraries, such as QUnit.
- The JavaScript project should be viewable in Page Inspector, since it includes HTML, CSS and JavaScript.
- It should also be possible to debug the project via Page Inspector.

If you run a .NET app that needs to talk to the web, and you're behind an authenticating proxy server, then that app will fail to talk to the web.

Internet Explorer and Google Chrome work, Visual Studio and loads of other Microsoft apps will work. They can all talk to the web. But every .NET-based app or website I've ever seen will fail.

The implications of this are profound. I've seen umpteen forum posts over the years where people are scratching their heads, wondering what's wrong. I've seen IT guys re-route their users thru special-case connections to the web, because the user has to access some web functionality.

I've installed a piece of software that needs to authenticate a license key over the web... only to fail. And then you have to call their support lines.

I've seen Umbraco and Orchard CMS users fail to access the online galleries of themes and widgets. No-one - developers, users, IT guys - have a clue what's wrong or how to fix it.

Even Microsoft's .NET apps fail: if I try to run WCF's svcutil.exe on a remote service, it will fail... because I'm behind an authenticating proxy server.

And yet the fix is so simple. Simple, but no-one knows about it... no-one! Take a look at this StackOverflow question:-

http://stackoverflow.com/questions/299940/how-should-i-set-the-default-proxy-to-use-default-credentials

The simple, simple fix is to add this to your .NET app's app/web config file:-
<system.net>
<defaultProxy useDefaultCredentials="true" />
</system.net>

But since no-one knows about this, let's end the years of confusion and have .NET 4.5 change the default value of useDefaultCredentials from false to true. Problem solved, and everyone can get on with their lives.

If Internet Explorer "just works", why can't .NET-build apps "just work"?

And for a better-argued case, see here:-
http://sticklebackplastic.com/post/2007/01/26/Poxy-proxies.aspx

Thank you.

The Metrics Power Tool for Visual Studio 2010 is not compatible with the version of FxCop that ships with Visual Studio 2012. It looks like the interface changes that cause the break are minimal.

We use the Metrics Power tool in our build process and derive a number of reports from the data gathered during the nightly builds.

Please release an updated version of the Metrics Power tool which works with FxCop 11 or release an updated installer of the powertool that includes the correct dependencies so that it can be used without having to install Visual Studio 2010 alongside it.

Additional feedback for the power tool:
- Please use the same class name formatting which is used in the Code Coverage tables inside TFS databases, that makes it a lot easier to use the output in the Reporting features.
- Please add the source file location of the method (from the pdb file) to the report as well to make it a lot easier to provide actionable warnings and errors in the IDE.

I'm sure there are many developers out there with "older" systems that are completely capable of running Windows 8 64-bit and Visual Studio 2012 but are not able to develop and test Windows Phone 8 applications because of Microsoft's choice to make the Windows Phone 8 emulator a Hyper-V virtual machine. There should be a mechanism to run the emulator using either VMware Player or VirtualBox which will use SLAT if it's present but will continue to work if it isn't or update Hyper-V to do the same.

I don't understand this choice as I am able to write applications for Windows 8 using the built in simulator and I would think that is more involved than developing for the phone. Making it MORE difficult to develop for the phone isn't smart when you need more apps to compete with other ecosystems.