The Artima Developer Community
Sponsored Link

.NET Buzz Forum
VS.Net multi language bug - 2.5 years and still going strong?

0 replies on 1 page.

Welcome Guest
  Sign In

Go back to the topic listing  Back to Topic List Click to reply to this topic  Reply to this Topic Click to search messages in this forum  Search Forum Click for a threaded view of the topic  Threaded View   
Previous Topic   Next Topic
Flat View: This topic has 0 replies on 1 page
Roy Osherove

Posts: 1807
Nickname: royo
Registered: Sep, 2003

Roy Osherove is a .Net consultant based in Israel
VS.Net multi language bug - 2.5 years and still going strong? Posted: Feb 18, 2004 3:32 AM
Reply to this message Reply

This post originated from an RSS feed registered with .NET Buzz by Roy Osherove.
Original Post: VS.Net multi language bug - 2.5 years and still going strong?
Feed Title: ISerializable
Feed URL: http://www.asp.net/err404.htm?aspxerrorpath=/rosherove/Rss.aspx
Feed Description: Roy Osherove's persistent thoughts
Latest .NET Buzz Posts
Latest .NET Buzz Posts by Roy Osherove
Latest Posts From ISerializable

Advertisement
This is indeed a very annoying bug, and arguably has high importance because being able to develop on multiple languages is one of VS.Net's most touted features. Annoyingly enough, this problem only happens when the Unifying GUI app is a VB.Net app, not C# one.
Does anyone from the VB.Net\VS.net team care to comment on why this problem, that has existed ever since the Beta 2(or beta 1) days of VS.Net has not been fixed up until today, and still exists in Whidbey?
 
[via Philip]

Read: VS.Net multi language bug - 2.5 years and still going strong?

Topic: [Article] Make your .Net application support scripting - the practical way Previous Topic   Next Topic Topic: Longhorn/XAML Property aliasing

Sponsored Links



Google
  Web Artima.com   

Copyright © 1996-2019 Artima, Inc. All Rights Reserved. - Privacy Policy - Terms of Use