• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 810
  • Last Modified:

Visual Studio 2005 DataSet Visualizer

I have recently moved my development environment to a Windows 7 machine.  I have 4 or 5 solutions that are written in Visual Studio 2005.  All were working fine.  Then, this past week, when I run one of those solutions in debug and try to view datasets, the dataset visualizer no longer shows up....it shows as some sort of XMLDiffGram object.  I can open any of my other solutions and debug them and the dataset visualizer is there.  So, I cannot figure out how to get that back in my other solution.  I have tried many things I have seen on the internet and nothing has worked.

It seems that it has nothing to do with my Visual Studio installation since some solutions don't exhibit this problem.

Any help you could provide would be great.  I will be on vacation for a few days, but wanted to get this out there and will respond when I return.

0
ablesa
Asked:
ablesa
  • 9
  • 7
  • 4
1 Solution
 
carlnorrbomCommented:
Hi,

When you moved your development environment to W7, did you also upgrade VS to the newest version? Did you choose to run the VS conversion to upgrade the solutions to a later version of the framework?

/Carl.
0
 
ablesaAuthor Commented:
no, i did not upgrade the solution... it is still in VS 2005...  but so are many of my other solutions that still work fine...
0
 
carlnorrbomCommented:
Hi,

Reason for me asking is there's sometimes issues with controls that change between the different version of the framework but it would seem this is not your case. I'm at a loss to be honest. What if you for testing purposes (please back up your solution first) were to copy the markup code for your dataset, delete it and create a new one in which you paste the copied code to re-create it?

/Carl.
0
[Webinar] Kill tickets & tabs using PowerShell

Are you tired of cycling through the same browser tabs everyday to close the same repetitive tickets? In this webinar JumpCloud will show how you can leverage RESTful APIs to build your own PowerShell modules to kill tickets & tabs using the PowerShell command Invoke-RestMethod.

 
ablesaAuthor Commented:
I'm not sure what you mean by copying markup code...  
0
 
carlnorrbomCommented:
Hi,

Make backup copies of the dataset files (*.xsd/*.xss), then delete the dataset from the solution within VS. Add a new dataset the solution with the same name, open the backup files through explorer, for instance in Notepad and then replace the content of the dataset files in VS with the code from the backup copies. You can right click the dataset designer surface and choose "View code".

/Carl.
0
 
ablesaAuthor Commented:
There is no such thing...  This is just a datatable that is defined in the code...  Like this:

Dim dtUsers as datatable

When I debug, I should be able to see a "magnifying glass" icon when I hover over that datatable and I should be able to click that and see the contents of that datatable.

I'm not sure you understand my problem...
0
 
carlnorrbomCommented:
Hi,

Ok, i misunderstood you then, I thought you where referring to strongly typed datasets. If you would have said datatable that is a completely different thing. In that case I am at a loss unfortunately.

/Carl.
0
 
ablesaAuthor Commented:
Yes, I saw that post, CodeCruiser...  It describes my problem to a "T", but unfortunately, nothing there helps.  Its just odd to me that it is only a problem in one solution.  I tried deleting my solution and pulling down again from source safe, but that doesn't help either...  Really odd...

Any other suggestions?
0
 
CodeCruiserCommented:
Did you read this comment?

I was really bothered by the problem, so I turned to Microsoft support, and they solved my problem! The short solution is that apparently one of the DLL's in the My Documents\Visual Studio 2005\Visualizers folder was corrupted. I deleted all the contents of the folder, and the visualizer came back.
The long answer can be found in this post written by Faruk Celik - the person from Microsoft who solved my problem.
0
 
ablesaAuthor Commented:
yeah.... i tried that too...  AGain, it works in all of my solutions except one and I assume they would all be using the same folders and visualizer dll's...  so, its wierd why this one solution has a problem.

thanks...
0
 
CodeCruiserCommented:
That to me means that the problem is with the configuration files of this project. Try deleting the SUO file (its hidden and do make a backup).
0
 
ablesaAuthor Commented:
well, i deleted it and opened solution and ran...  same thing....  I've attached a document that shows what it looks like in the problem solution and one that shows it correctly in another solution.
Visualizer-Problem.doc
0
 
CodeCruiserCommented:
Are you sure its a datatable? Did you try this on some other variable?
0
 
ablesaAuthor Commented:
YEs...      Dim mUsersCache As System.Data.DataTable

Any variable in the "bad" solution looks wierd...not just datatables...

In my good solution, it shows the type and value of any variable I hover over like its supposed to....
0
 
CodeCruiserCommented:
The only option left really is to create a new solution and add all the forms to it one by one.
0
 
CodeCruiserCommented:
You can use the immediate window by the way.
0
 
ablesaAuthor Commented:
Ok, I played with this some more and found the problem...  
The application was building for "any cpu" platform.  When I created a new configuration for the X86 platform and set that as the configuration for all of my projects, I now get the data visualizer and debugging works ALMOST like it should.  I still have an issue with my breakpoint not being recognized with the error "source code is different from the original version".  Haven't resolved that one yet, but I think I am on the right track now, at least.  Thanks for all your help CodeCruiser!
0
 
CodeCruiserCommented:
Glad you got it sorted :-)
0
 
ablesaAuthor Commented:
I found the answer myself but appreciate the thoughtful questions and tips from Code Cruiser.
0

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 9
  • 7
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now