Visual Studio DataSet Designer Saving VERY Slow

Question

Working with Visual Studio 2008 DataSet Designer has become a pain in * s. I have a fairly large data set (> 50 tables), and it takes a long time to save the chains (I say about 10-15 minutes here!). This may not be a hardware problem, as I have an Intel i7 operating system, 8 GB and 7,200 rpm. Does anyone have an idea? (This "error" occurs on every PC working with this data set).

Thanks!

Answer 1

Try to find a solution in another question .

Go to Tools -> Options -> Windows Form Designer and set AutoToolboxPopulate to false.

This works for me.

Answer 2

I have the same situation. We have over 100 table definitions in a dataset. When using WinXP, 5 out of 9 times the VS will crash during save due to OutOfMemoryException. The updated OS for Windows 7 (32) seems to speed up the designer’s savings and productivity. However, it still sometimes raises an OutOfMemoryException in Visual Studio during save. Usually I finish restarting VS, open only the dataset constructor, and then save the dataset.

I have a Duo Core with 4 GB of RAM. Saving a dataset takes 1 to 2 minutes. Not as slow as 10-15 minutes, but it is still slow. During the save, the designer regenerates the dataset.design.cs file. My designer file is about 9 MB. You may want to check the size of your designer and measuring instruments file if your VS saves this for a long time.

My suggestions: 1. If you have ReSharper installed, try disabling it if ReSharper analyzes the created constructor file. 2. Delete the created constructor file and see if the generation of the new one is faster. 3. Not sure if that matters. Check how complex your definition table is. This may be possible if you have some kind of pivot table relationship that slows down the creation of a designer file.

Answer 3

I know this is a late answer, but hopefully this will help someone else. When working with a designer, he works faster, without any other tabs except the designer. If you have a .cs file open with the designer, it will take him more time to perform simple operations, such as renaming the label.

I feel your pain when I am working on a project with a 100+ DataSet and I have the same problem.