Showing archive results for October 2014

As NuGet continues to gain momentum, more Microsoft teams have been seeking to install NuGet packages from their Visual Studio tooling. This began with ASP.NET, where NuGet was born, when project templates started coming with pre-installed NuGet packages. More recently, we've heard of teams all across Microsoft with tooling gestures that result in ...

We on the Web Tools team love hanging out with the community. We thought it would be cool to start sharing exactly where we will be and what conferences or user groups you can join us at!The .NET Developer Blog has a great always updated list of .NET User Groups, so be sure to bookmark that also!We’ve got two big events coming up soon, and th...

Updated (2017): See .NET Framework Releases to learn about newer releases. Today, we are announcing updates to the .NET Framework vNext, ASP.NET vNext and .NET Native. These are all available in Visual Studio “14” CTP4. This .NET Framework release contains RyuJIT, the next generation X64 JIT. ASP.NET vNext contains major improvements in the runtim...

Today we released updates for ASP.NET vNext in Visual Studio “14” CTP 4. This release includes the ASP.NET vNext runtime and tooling improvements as outlined below. ASP.NET vNext Runtime This CTP includes our alpha4 runtime packages for ASP.NET vNext. You can find details on the specific enhancements added and issues fixed in the publ...

As we work on some big changes for NuGet 3.x, we're finding that we're at a crossroads: Should we use .NET 4.5 and improve our Visual Studio UI using new features available in Visual Studio 2012, Visual Studio 2013, and Visual Studio "14"; or should we retain support for Visual Studio 2010? Visual Studio 2010 has been supported since NuGet's intro...

Have you ever seen this error before? Doesn't it make you want to yell and scream at NuGet, "Why did you just show it to me if I couldn't install it!?‽" Yeah, it makes us want to yell and scream too, so we decided to set about fixing it! Along with that, we've also discovered a bug we want to correct but unfortunately, it's a breaking change so...