Windows Develop Bookmark and Share   
 index > Windows Forms Designer > Designer will not open after downloading new VB 2008
 

Designer will not open after downloading new VB 2008

A program was created using VB 2008 Beta. I downloaded the new version. When I open the program in the new version I get errors when I open any of the designer pages. Thecode pages openand report no errors. The program will run in debug and will build to a good exe file. However, until I can open the designer pages, I cannot make needed changes in the program. The errors for one page are as follows:

________________________________________________________________________________________________

Instances of this error (4)

Could not load file or assembly 'System.Data.DataSetExtensions, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' or one of its dependencies. The system cannot find the file specified.

1.

Show Call Stack

2.

Show Call Stack

at BWver2008.BreyerResTextIndexDataSet1.InitClass()
at BWver2008.BreyerResTextIndexDataSet1..ctor()

3.

Show Call Stack

4.

Show Call Stack

Help with this error

Could not find an associated help topic for this error.Check Windows Forms Design-Time error list

Forum posts about this error

Search the MSDN Forums for posts related to this error

_________________________________________________________________________

Code Block

The variable 'BreyerResTextIndexDataSet' is either undeclared or was never assigned.

Go to code

Help would be appreciated. Sorry, the editor provided here does not seem to allow corrections or formatting.

Marvin Spiro

marvin spiro  Friday, November 23, 2007 11:29 PM

I used copy and paste to transfer the xsd query information. A few of the queries required further editing. I had only 3 tables in the project but the datagridviews were complicated and I did not want to have to reconstruct and re-edit them.

I tried the 2.0.0.0 version. It did not help.

Good luck.

marvin spiro  Monday, December 03, 2007 2:06 AM

I have the same error also with the same senario, yet I can locate the file in the add references dialog. but it doesn't seem to help.

Could not load file or assembly 'System.Data.DataSetExtensions, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' or one of its dependencies. The system cannot find the file specified.
Instances of this error (17)
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.

Jon Stroh  Sunday, December 02, 2007 8:39 PM

The file I found on the computer semms to be version 3.5 do I need to upgrade my project datasets somehow??

Jon Stroh

Jon Stroh  Sunday, December 02, 2007 8:45 PM

I finally solved my problem Even though the forms would not display correctly in designer mode, the program would run correctly in debug mode and would build an .exe file that ran correctly. However, I would not be able to ever update the program in its current state. I noticed that the Data Sources window was blank. I tried to populate it with my database file but it was not possible to do so. I finally stumbled in a way to fix the problem. In Solution explorer, I expanded to show all files and deleted all .xsd and data set designer files. I was then able to populate the Data Sources window, I thenopened the new .xsd files and configured new queries. After that all of my forms opened and there wereonly a few name changes to be made in the vb code for each form.

Marvin Spiro

marvin spiro  Monday, December 03, 2007 1:28 AM

Marvin that worked for me but I have 10 tables and about 20 queries and I hate to do all the rewrites. Hope we can find a better solution. Thanks for the tip, at least it will run, can't edit anything in the form but it will run. I wonder if using the version 2.0.0.0 is less effective than the 3.5.0.0 version. Will we be missing any additional functionally?

Coz

Cozmodon  Monday, December 03, 2007 1:54 AM

I used copy and paste to transfer the xsd query information. A few of the queries required further editing. I had only 3 tables in the project but the datagridviews were complicated and I did not want to have to reconstruct and re-edit them.

I tried the 2.0.0.0 version. It did not help.

Good luck.

marvin spiro  Monday, December 03, 2007 2:06 AM

I am still hoping for a better solution from MS. I saw some stuff about web apps and how to correct the problem but, I and I don't think you, don'thave a web app so it does not do us any good.

Keeping fingers crosed for MS and will be very upset if they don't gives us a solution.

Coz

Cozmodon  Monday, December 03, 2007 5:40 PM
I seem to have stumbled onto the answer to the problem that is VERY easily done.

I was able to duplicate all the erros stated; specifically that the Data Sources Window was blank; and the initial version 2 error each design window would throw.

After reading over the fix advice listed here, which basically states that one needs to completely rebuild the Datasets, I set out to do just that.

I, one by one, opened each DataSet Design Window and rearranged the Table and TableAdapter Objects so I could take a Print-Screen Snap-Shot of the page so I would have the Object/Query information. In each case I also saved the resulting new arrangement for each DataSet Designer Window.

For whatever reason, This simple act seems to have solved all the errors. The DataSet Window is now populated as it should be, and all forms open as they should.

I seem to be back in business once again.

I will be doing some immediate experimenting to see if there are any side effects, but I don't believe there is.

I will post any negative results.

Tom
TomTech71  Wednesday, March 12, 2008 7:18 PM

Wonderful!!

I found an old copy of my program that I had not already repaired with my much longer method and tried your method on that old version..

I opened each .xsd file and saved it. All of my forms opened in the designer window with no errors. The Data Sources Window was still empty but after I printed each of the .xsd windows the Data Sources Window was populated.

Thanks,

Marvin

marvin spiro  Thursday, March 13, 2008 5:40 PM

Hello,

I had sometimes the same problem if I inherit user controls from another user control and whyever VB 2008 is telling me he cannot load the parent user control from which many other user controls are inherited.

Often times, I clean the build (menu Build --> Clean <applic>) and build once more my complete solution. This works.

It seems to be an error within VB2008 (serialization).

Yours

Stephan

Stephan_MZ  Thursday, March 13, 2008 9:35 PM
I've seen that situation as well. Didn't know the fix though; Thanks.

On the original, posted, DataSetExtensions problem: I've been working the Datasets pretty heavily since the fix, and everything is fine.

Tom
TomTech71  Friday, March 14, 2008 4:27 PM
Same issue here - a C# Windows app created in VS205 - now using VS2008. The Form that cannot be opened has a user control. Looking at the call stack, it points to a dataset load from a table adapter within the User Control.

After searching the Microsoft built code and rebuilding the dataset, I still have the issue. It complains that the Login has failed for myself (<Domain>\<User>), but all other parts of the app are OK.

As above, if you do not ignore the issue and do not open the form further, it builds and runs OK
Pixelda  Monday, March 09, 2009 2:01 PM

You can use google to search for other answers

Custom Search

More Threads

• Embeded panel within a ToolStripControlHost is not available at design time
• designer.cs cleanup
• Floating toolbar interface
• how to draw a line on the form?
• Datecontrols (usercontrol)
• removing the focus rectangle from a flat button
• License a control
• Custom component selection problem
• Can System.Object be used as a User Setting
• UserControls not showing up in toolbox
Home          Copyright 2009-2010 by windowsdevelop.com All rights reserved