We had a user on Windows 8 Internet Explorer 10 get a "Input string was not in a correct format" exception on a legacy WebForms application. We did some research and found out that there is an existing bug in ASP.NET 4 with IE 10 and imagebutton controls not working properly when they are clicked.
One solution which doesn't require any code changes is to update the webserver with the .net framework 4.5 which will correct the bug. We did so on a test server and the bug goes away great!
My question is: Does anyone know of any risks that could come with this solution of installing the .net framework 4.5? Is there a list of other issues with Windows 8 IE 10 and ASP.Net WebForms or MVC that we should be aware of?
Details of the issue can be found here:
https://connect.microsoft.com/VisualStudio/feedback/details/755419/asp-net-4-0-and-ie10-click-on-imagebutton-in-updatepanel-produces-error-click-on-normal-button-does-not
Scott Hanselman described the issue over one year ago. The problem is a bug in a browser definition file where ASP.NET categorizes IE10 as an unknown browser.
The following hotfixes (.NET 2 and 4) should fix the described issue:
http://support.microsoft.com/kb/2600088
http://support.microsoft.com/kb/2600100
Installing the .net framework 4.5 on the servers fixed the issue and we didn't see any other problems.
Related
Is there any way to make Azure DocumentDb work with ASP.NET 5 (Core). I don't need to my application to work with Linux and Mac OS. I tried to target it to full .NET Framework but either I'm doing something wrong or it's not enough but I'm getting an error "the dependency could not be resolved"
Are you targeting both aspnet50 and aspnetcore50? I saw a similar issue last year where someone was targeting aspnet50 and aspnetcore50 and their DocumentDB app and getting errors, and by simply commenting out one, the app ran fine.
I've got a strange issue that's left me scouring Google for the past couple of hours, but I haven't found anything even close to this.
I have a VB.NET Winforms project containing a class that dynamically generates an image URL for a remotely hosted charting API, and returns the URL as the source to a PictureBox (pbCallChart.ImageLocation = MyURL). This has been in place and working fine for years now. However, I recently had to upgrade the project from .NET 3.5 to .NET 4.0 (I'm working in VS 2010 on a 64-bit build, which apparently won't let you do active debug in .NET 3.5). As soon as I did this, my image stopped showing up.
I verified that the image works when I pull up the URL in a web browser on the same machine that I'm working from. At first I figured maybe that property was removed in 4.0, so I tried switching to the Load() function. No dice. Then I took it one step further and wrote this little function:
Public Function ChartImage() As Bitmap
Dim ChartURL As String = "http://www.anyURL.com/img.jpg" 'Chart()
Return New System.Drawing.Bitmap(New IO.MemoryStream(New System.Net.WebClient().DownloadData(ChartURL)))
End Function
When I run this (and I've confirmed that it doesn't matter what URL I pass it), I always get the error:
An unhandled exception of type 'System.Net.WebException' occurred in System.dll
Additional information: Unable to connect to the remote server
I know this isn't a proxy problem, because it works fine on this same computer under .NET 3.5. And I've confirmed it's not just a debugging quirk, because I compiled executables and provided them to users - they confirmed that the .NET 3.5 version works and the .NET 4.0 version does not.
I can only assume that there must be some security configuration difference in the two versions that I don't know about, but it seems like someone would have mentioned it somewhere. Has anyone else ever experienced anything like this? I'm pretty much out of ideas - do you have any?
I'm trying desperatly to setup a MVC 4 (in the worst caes 3) with Razor on Monodevelop. I'm sitting on a Mac OS X machine, with Mono 2.11.4.
It seems to not have all the assemblies required. System.Web.Helper for instance, doesn't seem to be found. And MonoDevelop can only find System.Web.Mvc version 3 (With NET framework 4.5 selected) or version 2 (with NET Framework 4.0 selected). Does anyone know how to get MVC 4 with Razor to work?
(Razor pages worked with Mono, in theory, with version 2.10.x series, but you had to bundle Microsoft's assemblies with it into your Linux box.)
Since Mono 2.11.1, these assemblies are now bundled by default in Mono, because Microsoft open sourced Razor recently (on March 2012). So: you're using the correct version of Mono.
The catch is that, as explained in this blogpost, MVC4 depends on the async ASP.NET API stack, which is not ready yet in Mono. So yes you can now use Razor with Mono without the need to deploy MS assemblies from Windows, but, you need to stick with MVC3, not 4, for now.
(Copy-pasted my answer from this other stackoverflow question and tweaked it a bit.)
I modified the VS2010 MVC4 Project Template to run out-of-the-zipfile in Xamarin Studio/MonoDevelop on Mac & Linux: http://www.cafe-encounter.net/p1319/run-asp-net-mvc4-on-mono-monodevelop-on-mac-the-c-template-project.
Update: I've done a MVC4 on .Net 4.5 template with notes at http://www.cafe-encounter.net/p1510/asp-net-mvc4-net-framework-version-4-5-c-razor-template-for-mono-on-mac-and-linux including link to github.
According to the Compatibility page on the Mono site MVC4 is supported with the exception of the async features. Unless there is a part of the MVC4 framework that is uses async by default, then those new features will only be a problem if you have added that pattern to your code.
Microsoft came up with a solution to support Coded UI tests in Silverlight 4 applications.
Proposed solution in 2 steps and I did it. Steps are:
Install Visual studion 2010 feature pack 2.
Added SilverlightAutomationHealper.dll to my Silverlight 4 project.
I build the project and tried to record CUI tests but failed. I found an error message
"No Silverlight controls were detected. Verify that the application under test is built using Silverlight assemblies wiht a version of 4.O or greater and that a reference to the Microsoft.VisualStudio.TestTools.UITest.Extension.SilverlightUIAutomationHelper.dll assembly has been added to the project. For more information, see http://go.microsoft.com/fwlink/?LinkId=204562" raised.
This issue really annoying us, can anyone plese help me.
Thanks,
Jaji Alapati.
If your controls are named correctly (x:Name), then an other issue might be there with the test execution. If you use Internet Explorer to run tests, you have to run IE in compatibility mode (turn the compatibility mode on in the URL section of the browser). This might solve your problem.
I'd like to use ELMAH in an ASP.NET MVC 2 application running on .NET 4, but according to the project hosting site on Google code, it only supports .NET 1.1 and 2.0.
Is there a .NET 4 version of ELMAH already, or do I have to download the source and update whatever breaks myself?
Elmah works perfectly fine for ASP.NET 4.0.
However, there are a few tricks in getting it setup to work perfectly on an MVC website.
I have recently starting blogging about this topic so be sure to check out my blog series on logging in MVC. The first article covers getting Elmah set up and running for MVC using all the tricks that you can find about it on StackOverflow.
There is a link to downloadable code at the end of the article. Hope that helps.
http://dotnetdarren.wordpress.com/
I am using .NET 4.0 and I dont about a new version.... but I am using the elmah 1.1 and it works....:)..You may have to change source though to add custom fields or log additional values..which is bit of a pain...but get started here
Well it's open source nothing should prevent you from recompiling it using the .NET 4.0 framework.
This link has some information about running pre .NET4 web apps and .NET4 web apps in a server.
EDIT:
Actually you won't need to recompile ELMAH. According to this and this article the In-Process side by side execution should do the trick.
I had the same question so I downloaded the 1.1 src, opened it up in visual studio 2010, changed the project to target 4.0 and rebuilt it. I then dropped the dll in my ASP.NET MVC 2.0 app and it has worked fine.