Ferry Meidianto | /* Living in .NET World */

TAG | asp.net

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.

VS2013VS2012

· ·

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.

·

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?)

image

and voila! it got its awesome performance back!

· · · ·

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

·

I shocked when I found that I couldn’t access Umbraco control panel of one of the most important websites that my client has. It threw “Object reference not set to an instance of an object” error once I successfully logged in to the control panel.

image

After making backup and small research I found a way to recover from that annoying thing. The workaround was recycling the Application Pool that the website use.

·

Older posts >>

Theme Design by devolux.nh2.me

Disclaimer

All postings/content on this blog are provided "AS IS" with no warranties, and confer no rights. All entries in this blog are my opinion and don't necessarily reflect the opinion of my employer or sponsors. The content on this site is licensed under a Creative Commons Attribution By license.
To top