A first hand look from the .NET engineering teams
As Brian Harry recently announced, there will be a Visual Studio 2012 Update 4. With RC2, we’ve updated the NuGet support. In this blog post, I’ll summarize those improvements.
The RTM version of Visual Studio 2012 included a fairly old version of the NuGet client (2.0). Although the NuGet team regularly ships updated versions via the Visual Studio gallery, many of you haven’t updated your NuGet clients yet – probably because you weren’t aware that an update exists or because you didn’t see a reason to update.
Unfortunately, the NuGet 2.0 client didn’t support portable class libraries (PCL). Most of our packages make use of PCLs which in turn has resulted in many customers reporting bugs that they weren’t able to install our packages in their projects.
RC2 brings NuGet 2.6 (which was the latest version at the time we finalized the work for RC2). This version of NuGet includes two fixes that we believe are most relevant for our customers:
Support for portable class libraries. This fixes the package installation issues.
Allows package authors to specify a minimum version of NuGet. This enables us to explicitly indicate a NuGet update is required to consume one of our packages, and customers that aren’t consuming our packages are not forced to update. This also addresses the issue for build servers. If they have a checked-in version of nuget.exe that is older than what is required the build fails with an actionable error message.
Extension and Updates Dialog after installing VS 2012.4 RC2
Since more and more functionality of the .NET Framework is published as NuGet packages, we’ve added a curated feed. This feed contains all the official Microsoft and .NET NuGet packages and allows you quickly find our packages.
Previously, this feed was only available in Visual Studio 2013. VS 2012.4 RC brings this feed to Visual Studio 2012 as well.
The “Microsoft and .NET” NuGet feed
Visual Studio 2012.4 RC 2 includes an updated NuGet client which supports portable class libraries as well as our new curated feed for official Microsoft and .NET NuGet packages.
Please download RC2 and tell us what you think!
Did you fix theGUI? Did you bring back setup and deployment projects?
@ThomasX: I'm not working on the Visual Studio team, so I can't speak authoritatively about plans, but I'm not aware of any major changes in the UI or deployment projects in VS 2012 Update 4.
I tried downloading it and running with the "/layout" parameter, and it gets stuck on:
And that's as far as I can get... whether I choose to search for the package on the internet or not, it dosn't find it. There are only 3 options, search for package on the internet, locally (when I am *downloading*?), or Cancel.
@Jerome: I'm not sure what you mean. Is the VS2012.4 RC2 setup stuck?
Guys its being more than 13 years of requesting this technology, but none of the Microsoft teams has implemented XPath 2.0 and XSLT 2.0. We need OOTB support for XPath 2.0 and XSLT 2.0 in dotnet and SharePoint.
XSLT 1.0 is not enough with its implicit way of doing complex operations when W3 is finalizing XSLT 3 specifications (http://www.w3.org/TR/xslt-30/)
Microsoft can acquire http://exselt.net/ or other companies to save the human resource and time.
@abm: Thanks for the feedback. We currently don't have any plans to add XPath 2.0/XSLT 2.0 support. You can vote for it here: visualstudio.uservoice.com/.../3795831-native-support-for-xpath-2-0-or-xslt-2-0-in-net
Dear .NET team, please implement best and most optimized algorithm for Age() in DateTime class. Being a common problem and due to its inherit complexity (stackoverflow.com/.../863980), please consider it for .NET framework:
This definitely would make sense if "current age" of any DateTime object can be retrieved and the function is defined in the DateTime class. This would bring great deal of value to .NET framework.
you have any queries please visit www.kbreducation.com