.NET Fx Bugs
Bugs found in the current version of the .NET Framework.
If you find one drop me a message!
A nasty one, you will probably realize in front of customers.
The workaround can be found on the Windows SDK blog.
Enjoy!
Microsoft released a hotfix [1] for Visual Studio 2008 (also targeting Visual Web Developer Express) that corrects several issues with the web development features.
At this time the hotfix is only available for the English and Japanese versions.
List of things that were corrected according to this post [2] by Vinaya Reddy:
HTML Source view performance
- Source editor freezes for a few seconds when typing in a page with a custom control that has more than two levels of sub-properties.
- “View Code” right-click context menu command takes a long time to appear with web application projects.
- Visual Studio has very slow behavior when opening large HTML documents.
- Visual Studio has responsiveness issues when working with big HTML files with certain markup.
- The Tab/Shift-Tab (Indent/Un-indent) operation is slow with large HTML selections.
Design view performance
- Slow typing in design view with certain page markup configurations.
HTML editing
- Quotes are not inserted after Class or CssClass attribute even when the option is enabled.
- Visual Studio crashes when ServiceReference element points back to the current web page.
JavaScript editing
- When opening a JavaScript file, colorization of the client script is sometimes delayed several seconds.
- JavaScript Intellisense does not work if an empty string property is encountered before the current line of editing.
Web Site build performance
- Build is very slow when Bin folder contains large number of assemblies and .refresh files with web-site projects.
Make sure to read the installation instructions at [2].
Enjoy!
[1] https://connect.microsoft.com/VisualStudio/Downloads/DownloadDetails.aspx?DownloadID=10826
[2] http://blogs.msdn.com/webdevtools/archive/2008/02/09/downloadable-hotfix-performance-and-editor-fixes-for-microsoft-visual-studio-2008-and-visual-web-developer-express-2008.aspx
Larry asked in the MSDN Forums why the following command line:
svcUtil http://localhost/MyService.svc?wsdl /dconly
raises this error:
Error: The input read from 'http://localhost/MyService.svc?wsdl' is inconsistent with other options.
The essential note is stated in the Windows SDK Release Notes (Link):
5.4.11 Service Model Metadata Utility Tool (SvcUtil.exe) Can’t Generate Data Contracts from a Running Service
An example at the end of the svcutil.exe help output indicates that you can use the /dataContractOnly (/dconly) option to generate Data Contracts from a running service:
svcutil /dconly http://service/metadataEndpoint
- Generate Data Contract types from a running service or online metadata documents.
This usage does not work. You can only use the /dconly option to generate Data Contracts from local metadata files.
Microsoft released an update for enabling .NET Framework 1.1 applications to use the SendKeys command under Windows Vista without experiencing the "Hook cannot be created" error message (as explained in this KB article).
Interesting Microsoft Knowledge Articles on ClickOnce
Did you use ClickOnce with .NET Framework 2.0 and got the error message "Proxy authentication required"?
Are the accessing machines configured to use a proxy server that requires authentication?
If you answer both questions with YES: then you found a bug.
The good news is - there is a solution. You can request a fix (free of charge) at a Microsoft support holine and it will be (e-)mailed to you:
KB Artikel 917952: FIX: Error message when you try to install a ClickOnce application that you created in the .NET Framework 2.0 onto a client computer that is configured to use a proxy server: "Proxy authentication required"
After installing .NET Framework 2.0, No-Touch Deployment apps (HREF-EXEs) are broken. When you try to navigate to the EXE via a URL it prompts the user to Run or Save the EXE instead of launching it with IEExec.
See the bug details on MSDN Product Feedback Center
Update #2:
Microsoft finally released a KB article about this topic here.
Update:
Microsoft decided not to support HREF Exes from the Internet Zone in the .NET Framework 2.0.
It is known that this is disruptive to people that were using the feature, and there are several approaches to working around this limitation as described in the "Workarounds" section of this page.
- Add site to Intranet Zone or Trusted Sites Zone
Workaround Description:
Add the site being used to the Intranet Zone or Trusted Sites Zone.
The restriction on HREF Exe usage only affects the Internet Zone.
Workaround Steps:
If you are not familiar with adding sites to zones follow this instructions.
- Use browser controls
Workaround Description:
Use browser controls to run the same code. There is support for OBJECT tag browser controls which will run in IE against .NET Framework 2.0. You can load the original HREF Exe application via the browser control, although it will not run in a separate process any more.
Workaround Steps:
If you are not familiar with .NET browser controls hosted by Internet Explorer see this MSDN Mag article and this this KB HOWTO.
- Migrate to ClickOnce applications
Workaround Description:
Ideally, migrate to ClickOnce applications (it is absolutely understood that this is not a simple request, but ClickOnce applications are the preferred way for launching code through the browser).
Workaround Steps:
To find out more about ClickOnce in the .NET Framework 2.0 refer to this website.
- Configure Registry Key to allow HREF EXEs from the Intranet Zone (not recommended)
Workaround Description:
Configure the following registry setting on the client machines:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework]
"EnableInternetHREFexes"=dword:00000001
Workaround Steps:
Create the registry value as stated in the description on all client machines.
The bug sometimes occurs if you use the Response.Redirect method and pass false as endResponse parameter.
Workaround: Use true as endResponse parameter.
Resolution: A fix that can be requested is available.
See description at KB 888418 FIX: Users receive an "Object moved to here" error message when they open an ASP.NET Web page in the .NET Framework 1.1.
The primary focus of Microsoft .NET Framework 1.1 Service Pack 1 (SP1) is improved security. In addition, the service pack includes roll-ups of all reported customer issues found after the release of the Microsoft .NET Framework 1.1. Of particular note, SP1 provides better support for consuming WSDL documents, Data Execution prevention and protection from security issues such as buffer overruns.
Download: .NET Framework 1.1 Service Pack 1
Download: .NET Framework 1.1 Service Pack 1 for Windows Server 2003
More Information
KB 867460: List of bugs that are fixed in the .NET Framework 1.1 Service Pack 1 (SP1)
KB 318785: Determine wheather service packs are installed on the .NET Framework
SYMPTOMS
The MergeMenu method of the MenuItem object modifies both the source MenuItem objects and the target MenuItem objects. The result is that the same items are in both the source MenuItem objects and the target MenuItem objects.
"Armin Zingler" <az.nospam@freenet.de> wrote in message
news:uO5pjJTUDHA.2520@tk2msftngp13.phx.gbl...
> Hallo NG,
>
> ich setze die Cursor-Eigenschaft eines ListViews (lvw.Cursor =
> Cursors.AppStarting). Es wird aber immer der Standard-Cursor angezeigt.
> Warum? Es nützt auch nichts im MouseEnter und MouseMove den Cursor zu
> setzen.
>
> Armin
>
"Ryszard Gawron [MS]" <rysiekg@hotline.com> schrieb:
Hallo Armin,
das ist ein Bug und sollte bei der nächsten Version von Visual Studio .NET
gefixt sein.
Viele Grüsse
Ryszard Gawron
Microsoft Developer Support