Hi drbodzin, and welcome to the forums.
Please tell us which version of Visual WebGUi you are running?
This issue you reference, was checked against version 6.3.1, so in case you are running 6.3.0, I suggest you upgrade to the newest most stable version, currently 6.3.6 and see if you still have the problems.
Please make sure you completely clear all your cache, which is often the explaination of such problems. Please follow the below procedure to make sure you cache is completely cleared:
1. Shut down VS if it's running
2. Delete your browser cache (IE=Delete temporary internet files FF=Clear Private Data + Cache)
3. Go to 'C:\WINDOWS\Microsoft.NET\Framework\<Your relevant framework>\Temporary ASP.NET Files, delete all Visual webGui files.
4. Reset IIS if app will not be run within VS Dev webserver
5. Open sample application
6. Delete obj and bin folders (and ClientBin if SilverLight deploy)
7. Delete all Gizmox references
8. Reference the Gixmox DLL's, which now should be correct version
9. Temporarily set "Disable Caching" in General tab of VWG integration (remember setting back if production app). This is equiv to web.config setting:
<add name="VWG_DisableCachingSwitch" value="1" />
10. Increase private version of project
11. Clean
12. Recompile
13. Run in Dev Web server
If you still have problems, then the best way to describe those problems is by creating a most minimal application that demonstrates the problem(s) and then send your application to support [at] visualwebgui [dot] com with a link to this forum thread, along with some description about how to reproduce the problem.
Please also clean the solution before compressing it and reply to this post after sending, so we will know to check for your support request.
If connection to database is needed, please make sure you will be using the MSSQL Northwind sample database for your connection(s)
Remember to include information about what VWG version you are using, as well as you Visual Studio version+type and operating system version.
Palli