Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / Visual Studio.NET / IDE / March 2005

Tip: Looking for answers? Try searching our database.

IDE changes file SubType from "form" to "code", any fixes???

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Julie - 07 Sep 2004 19:41 GMT
The IDE has a nasty habit of changing the code type from "form" to "code" in
the project file on occasion.  This isn't the consequence of
migration/conversion from vs 02 to 03, but just seems to occasionally happen.
It happens on several of my development machines, and I can't find a pattern.

I've search Google Groups, but haven't found a definitive answer as to what
causes this and why...

The best workaround I've found so far is to open the form file (as code!) in
the IDE, change the inheritance (like add a space, then Ctrl+Z) and the project
recognizes the changes and restores the type back to form.  This is fine for 1
or 2 files, but my projects have 100's of files that this happens to on a
regular basis...

Anyone have any pointers/comments on this wonderful 'feature' of the 13th rev
of the IDE???
New Dot Net User - 20 Sep 2004 15:40 GMT
I tried changing 'code' back to 'form' without success and changing
the inheritance didn't work either. I finally got the form back by
doing a rebuild all. I don't know if that will work for you, but it
helped me.

>The IDE has a nasty habit of changing the code type from "form" to "code" in
>the project file on occasion.  This isn't the consequence of
[quoted text clipped - 12 lines]
>Anyone have any pointers/comments on this wonderful 'feature' of the 13th rev
>of the IDE???
pogi - 14 Mar 2005 23:56 GMT
Any updates on this problem? It seems that this issue is quite common but
amazingly I haven't heard any solutions for it.

I seems that this happens to classes that are extending an inherited form.
Forms that directly inherit from System.Windows.Form don't seem to have the
problem (at least that's what I've noticed).

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.