Although it’s recommended that we install Visual Studio versions in the order in which they were released (for example, install Visual Studio 2012 before we install Visual Studio 2013) as mentioned in http://msdn.microsoft.com/en-us/library/ms246609.aspx, there is possibility that we have installed Visual Studio 2013 before we know that we need to install Visual Studio 2012.
It happened to me last month. I actually more than happy to have Visual Studio 2013 only in my computer as I can also use it to open Visual Studio 2012 projects. But in the end I need to install Visual Studio 2012 because one of my teams are using Visual Studio 2012 and I don’t want any incompatibilities or project upgrades affect them.
If you have to install Visual Studio 2012 after Visual Studio 2013 for any reason, don’t worry, it can be installed without any issue.
I have been using this configuration almost a month and there is no issue at all. I mostly use them to do ASP.NET projects (and related, such as class library, etc) and I’m sure there is no issue with other project types too.
You can find the original announcement on .NET Web Development and Tools Blog
The NuGet packages for ASP.NET MVC 5.1, ASP.NET Web API 2.1 and ASP.NET Web Pages 3.1 are now live on the NuGet gallery!
Download this release
You can install or update to the released NuGet packages for ASP.NET MVC 5.1, ASP.NET Web API 2.1 and ASP.NET Web Pages 3.1 using the NuGet Package Manager Console, like this:
- Install-Package Microsoft.AspNet.Mvc -Version 5.1.0
- Install-Package Microsoft.AspNet.WebApi -Version 5.1.0
- Install-Package Microsoft.AspNet.WebPages -Version 3.1.0
Pre-requisites for this release
- If you are using Visual Studio 2012, please download ASP.NET and Web Tools 2013.1 for Visual Studio 2012.
- If you are using Visual Studio 2013, please download Visual Studio 2013 Update 1. This update is needed for editing ASP.NET MVC 5.1 Razor Views.
What’s in this release?
This release is packed with great new features summarized below:
ASP.NET MVC 5.1
- Attribute routing improvements
- Bootstrap support for editor templates
- Enum support in views
- Unobtrusive validation for MinLength/MaxLength Attributes
- Supporting the ‘this’ context in Unobtrusive Ajax
- Various bug fixes
ASP.NET Web API 2.1
- Global error handling
- Attribute routing improvements
- Help Page improvements
- IgnoreRoute support
- BSON media-type formatter
- Better support for async filters
- Query parsing for the client formatting library
- Various bug fixes
ASP.NET Web Pages 3.1
- Various bug fixes
You can find a complete listing of the features and fixes included in this release by referring to the corresponding release notes:
Tutorials and other information about this release are available from the ASP.NET web site (http://www.asp.net).
Questions and feedback
Ready to prove your expertise with the globally recognized MCSD (Microsoft Certified Solutions Developer) certification? Get started today by requesting your free MCSD ‘3-for-1’ exam voucher.
When you schedule and pay for the first exam using your personal voucher code, you’ll get the next 2 exams for free, valid on exams for any of the following certifications:
MCSD Windows Store Apps-HTML5
MCSD Web Applications
MCSD SharePoint Applications
MCSD Windows Store Apps-C#
MCSD Application Lifecycle Management
Act quickly; this is a limited time ‘3-for-1’ offer that ensures although the exams may test your talents the investment won’t break the bank.
The MCSD ‘3-for-1’ offer is available until May 31st, 2014*. All exams must be scheduled and completed by May 31st, 2014.
*Or while supplies last.
Review the offer Terms and Conditions.
Today I was debugging ASP.NET website and got very annoying issue. The website has file download feature and anytime I download the file IE9 couldn’t open it – the file was missing before the PDF application could open it. It did work on FF and Chrome.
I have cleaned-up Temporary Files directory and also ASP.NET temporary files (C:\Windows\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files) but no luck.
Later I realized that by changing the debugging port for ASP.NET Development Server to any new number solved the problem. But I didn’t believe that it’s the real solution. Then after playing with IE settings a bit I found that this setting caused the problem.
It was set to Automatically by default.
You can set it to Every time I start Internet Explorer but I prefer Every time I visit the Webpage for my need, both will work.
Hopefully this will help anyone having the same issue as I faced.
WebMatrix is a free web development tool from Microsoft that includes everything you need for website development. Start from open source web applications, built-in web templates or just start writing code yourself. It’s all-inclusive, simple and best of all free. Developing websites has never been easier.
Create, customize and publish websites for free with WebMatrix !
Has just got an email from Microsoft Most Valuable Professional program that my MVP is renewed. This will be the 2nd year as Microsoft MVP but this year I’m awardedÂ forÂ ASP.NET expertise. I’m hoping I can contribute more this year to the community.
Happy new year.
I recently upgrading ASP.NET MVC 2 solution from Visual Studio 2008 to Visual Studio 2010 (Ultimate Edition). I found that debugging was very slow. Depending on project size, it took around 30 seconds to initialize and another 5 seconds on each page request in my experience.
I tried disabling IntelliTrace (what is IntelliTrace?)
and voila! it got its awesome performance back!
After long wait, at last Windows Live Essentials 2011 reaches its RTM. There are 2 installer versions we can use:
Today I had chance to install it. Everything else went smooth but I got msnmgr.exe error when I was ‘first time’ starting the Windows Live Messenger.
The error says The program can’t start because wldlog.dll is missing from your computer. Try reinstalling the program to fix problem.
The error message was only thrown once. But after that every time I tried to login to Messenger it threw error 80040154. The solution link that leads to msxml3.dll fix didn’t help at all for this version nor reinstalling the Windows Live Messenger.
After long day of research, at last I got the solution. It seems the new Windows Live has grouped the wldcore.dll and wldlog.dll (used by Messenger, Contacts and Mail) to a folder c:\Program Files\Windows Live\Shared
Maybe because I did upgrade install it screwed up things.
The solution was simply copy paste those 2 files wldcore.dll and wldlog.dll from c:\Program Files\Windows Live\Shared to
- c:\Program Files\Windows Live\Messenger
- c:\Program Files\Windows Live\Contacts
- c:\Program Files\Windows Live\Mail
Now I can login to Windows Live Messenger and enjoy the whole Windows Live Essentials 2011 products.
Make donation to this article:
UPDATE (2010-09-29): Microsoft has release the fix. It should be available through Windows Update.
More Info: http://weblogs.asp.net/scottgu/archive/2010/09/28/asp-net-security-update-now-available.aspx
Microsoft Security Advisory just announced a vulnerability in ASP.NET that can lead to information disclosure. You can read the complete announcement at http://www.microsoft.com/technet/security/advisory/2416728.mspx
Important: Please make sure you read the Workaround section and do appropriate action based on your websitesâ€™ config.
Additional information can also be found at Scott Gu’s blog post http://weblogs.asp.net/scottgu/archive/2010/09/18/important-asp-net-security-vulnerability.aspx
Disk Cleanup tool is not installed by default on Windows Server 2008 R2. To make it available, you need to add a feature called Desktop Experience.
Note that in the screenshot above it listed as Installed because I have just installed it.