In the following image there is a standard windows TrackBar and two KryptonTrackBar instances. Can you spot which is which?
As you can tell the control is not quite finished as yet. The control is fully working allowing you to use the mouse to move the marker, use the keyboard and even responds to the mouse wheel. Now I just need to hook it into the rendering engine and add some code to actually draw appropriately.
With great relief I managed to work out the problem and as luck would have it I solved the problem just 10 minutes before Microsoft support called me to investigate the bug report. Thanks to Lex Li for pointing me at the support website instead of the connect site for reporting the issue.
So what was the problem? I already had VS2008 installed and had setup the symbol server settings so I could step into and see the source code for the framework Windows Forms code. This has been very handy in the past for tracking down problems by allowing me to see exactly what was happening in the base classes. Reflector is an excellent tool but there is nothing quite like stepping through the real code.
Well it seems that VS2010 was using the already defined settings and this was the cause of the issue. I removed the symbol server settings and it all working perfectly. Put them back again and it takes essentially forever to try and start-up debugging an application. It never occurred to me until I checked that VS2010 would automatically be using the same settings as defined in VS2008. I just assumed you had to set them up manually for each Visual Studio version.
A quick update on the VS2010 problem. As recommend by commenter’s I have added a bug report on the Microsoft Connect site. If you want to vote the bug upwards it might have a greater chance of being investigated… (hint hint)…
Microsoft Connect - Bug Report
In the meantime I have restored a system image that I prudently took immediately before the install and so I’m back again working away although only with VS2008 at the moment. Even-money says the fix from Microsoft will be to wipe the machine and install everything from scratch. Not something I am looking forward to doing as it takes a couple of days to get everything up and running to the point of being able to build Krypton automatically again.
Like a million other .NET developers I rushed to download the Visual Studio 2010 release and installed it on my machine. I hope I’m the only one that finds it’s seriously broken when trying to work with a Windows Forms project.
All I have to do is the following…
1, Startup VS2010
2, File -> New -> Project ->
3, Select C# -> Windows Forms Project template
4, Press F5 to compile and run
And then wait forever because after compiling it never runs the application. It makes no difference if I select the .NET Framework 4.0 or 2.0 or any of the others. They fail all the same. It makes no difference if you run as administrator or indeed any other setting I can think of. It’s just plain broken.
I sometimes also get the following error…
Now I find it hard to believe that something so basic would be broken so I must assume it is the setup of my machine helping to expose the problem. I have Windows 7 Professional 64bit with VS2005, VS2008 and now VS2010 all working side by side. Is anyone else using a similar setup and finding it does or does not work with the above steps?
The release is mainly intended for commercial customers.
In particular it fixes problems with using the installed source code for purchased version of the Suite. Previously the design time experience when using the compiled source code would fail. This has been resolved by having the source code compilation use a strong key and then automatically installing the newly built assemblies into the GAC. So now your projects can always use the GAC assemblies for your projects and the design time experience will be as expected.
Please download using the following direct link…
Major Change
– Installed source code now compiles with strong key
– Installed source code build places assemblies into GAC
Bug fixes
– KryptonRibbon generated code was causing compile errors
– KryptonWorkspace load config was not adding created pages
– KryptonMonthCalendar weeks numbers were incorrect
