Musings by Generator

I follow Scott Hanselman’s blog and he is a Microsoft fundi, he works for them and he posts regularly about the goings on at Microsoft. One of his posts recently caught my eye and I was glad to see it.

The .Net framework team are allowing people to test the latest Beta release of the .Net 4 client profile via the windows update. The update will be a recommended update when it is officially released about 6-8 weeks after the release of .Net Framework 4.

Below is  comparison of the 4 client profile and 3 client profile.

if you want to test the Beta, then here is how you go about it:

if you have no dot net 4 bits on your machine, Just make a text file with some meaningful name and make sure the file extension is .reg, and put the following text in it:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4B2WU]"OptIn"=dword:00000001

then save and close it, and double click on the file and it will insert the registry key and you will be able to install the client profile from windows update.

You can do it from an administrator command prompt if you want:

reg.exe add "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4B2WU" /v OptIn /t REG_DWORD /d 1 /f

I have heard that if you have any .net 4 components installed already, that the client profile will not install.

When they release the client profile it will install over the beta install and will upgrade it.

If you experience any problems, just remember it can be uninstalled, but do report any issues you have at The .Net Framework 4 Setup & deployment support forum.

We develop quite substantial applications for our clients, and we are using typed Datasets in the project I am on. Not the best option I know, but the option that was chosen.

Normally, I have only but praise for Visual Studio, but today I am extremely frustrated and wondering if it is really worth the money.

We are only half way through development on this application, we are actually busy with Change Requests from the client, but once we are finished with these we will be starting the next development phase. In that phase we will be adding in a massive section with brand new database tables etc etc etc. So our datasets are going to be growing by a large amount.

The issue that has caused my blood pressure to go through the roof today is this:

I opened up one of the datasets we use to delete two tables, and add them back in since the schema on the database counterparts had changed. when I deleted them, and then tried to save the delete. Visual Studio hung and when it came back about 10 minutes later, it kindly informed me that there was not enough memory to save the dataset, so I saved again and watched my memory usage while it was saving, it never hit 50%. So it is not a memory issue then. I tried a third time to save and this time it told me it can not save the Designer.cs file for the dataset, and asked me to select a location and file name for it. so I saved it as DataSet1.Designer.cs and it was happy.

I closed down visual studio, browsed to the location of the generated designer.cs and the one i saved opened them both up in notepad, and copied everything in my designer.cs to the generated one. Saved it and then opened up the Data Project in Visual Studio again. Deleted my designer.cs from the project and then rebuilt the solution. All fine and well.

So this prompted me to do some testing. I have two other Datasets in this solution, one that is very small, about 2 MB’s, and another that is of a similar size to the one I wanted to edit. So I went and did the same actions on both these datasets. on the small one, I had no issue, on the large one I got the same issue as I got earlier.

So after doing some more digging, I can only come to the conclusion that Visual Studio can’t handle Datasets that have a designer.cs file of more than 15 MB. To me this is ridiculous as there must be countless teams out there, using typed Datasets like us, who have datasets greater than 15MB.

To prove my point, we have an internal tool that generates Datasets for you. So I used the tool to generate it’s own files that it uses to generate Datasets, made my changes that I wanted to make, and then told the tool to generate my Dataset. this tool gave me no issue what so ever about saving the files, out of memory exceptions nothing, and it uses the cmd line tools that come with the Dot Net Framework.

So, if you ever think that you will have very large Datasets, you are better off spending your money else where. STAY AWAY FROM VISUAL STUDIO !!!!!