VB6 migration sky
 
  Forum  General Visual ...  Let's Chat Abou...  A few designer issues
Previous Previous
 
Next Next
New Post 3/31/2009 7:01 PM
Resolved
  seeker_01
8 posts
No Ranking


A few designer issues 

Hi,

Just want to put these issues up while using VWG. And what I did that seems to solve it.

Issue 1

After installation of the VWG with sources, in existing project, the designer is suddenly broken, all forms that was created in designer is having an error page instead. Error message: "Unable to cast xxx object to zzzz". Seems like random error. Some time I just get blank form but all controls are still there. And the application still works.

What seems to be the solution -

Follow the tutorial steps here. For existing project with older VWG version, make sure the current references in your project is refer to the Gizmox.WebGUI.Forms.References.
Note: Delete the existing references in your project's bin folder, then refer the Gizmox-references dll files. If you did not delete the existing reference file, VS 2008 seems to keep refering back to the current project bin folder even when I choose Gizmox-references dll file.

 

Issue 2

The property grid went blank at random. Once it went blank, if select the control using the property grid dropdownlist of control. it will cause VS to close. restart will fix it.

What I did to avoid restarting.

Simply Ctrl+S to save the file. Close it. Open another form in designer (not sure if the same form will do). Then, the property grid is filled up again. If it didn't, last option is to restart. Hope this might help cut down the restarting time until someone find out the main cause of this problem.

 

Issue 3

Sometime when I select an existing control on the form and deletes it using "Delete" key. The controls is actually left in the Form.designer.vb. Is this a known issue?

I have to go into the designer to actually clean out the deleted controls. It is not a major thing but kinda annoying to make sure it's deleted.

Anyway, hopefully this thread might help.

 

Cheers.

 
New Post 4/1/2009 12:43 AM
  lmp014
24 posts
No Ranking


Re: A few designer issues 

Hi,

I'm using the latest VWG Studio Express(6.3.6a) and suffer from annoying designer problems. The size of some controls are modified by the designer. Seems to be controls wich are anchored.

To help in debuging :

The form contains a splitcontainer and controls which are anchored to the right side of the form.

What happens :

You do your design and anchoring, run for debuging, and at some point in time, when you return to the designer view, the size of the anchored controls have increase too much (like retaining the values calculated at run time to properly anchor the form). From there, even if you resize properly the controls in the designer and save your form, it will show in debuging run with those erroneous size values. Or if you close and reopen the form, the erroneous size is kept.

Very annoying because it scraps your layout. If you get to fix it, after few other design changes it can happen again.

Any idea how to avoid it ?

 
New Post 4/1/2009 2:29 PM
  palli
6067 posts
1st Level Poster




Re: A few designer issues 

Hi guys,

Seems like all of those problems have been reported before.

  • seeker_01 / issue 1: You are correctly refrencing the article on how to use VWG with sources. Whenever you open a project that used an earlier version of VWG, it is a best practice to remove all the references to Gizmox DLL's, rereference them, increment privte version by 1, clean your project and recompile. Please see my standard recommendation for such procedure near the end of this message.
  • seeker_01 / issue 2 here (not exactly yours, but a similar designer refresh issue)
  • seeker_02 / issue 3 here (also, partly the same as issue 2)
  • imp014 problem here

Thanks for reporting though,

Regarding the standard procedure I recommend when changing VWG version... here it is:

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)
10. Increase private version of project
11. Clean
12. Recompile
13. Run in Dev Web server
 

Palli

 


Páll Björnsson - Visual WebGui support team - Email: support@visualwebgui.com
 
New Post 4/1/2009 6:44 PM
  seeker_01
8 posts
No Ranking


Re: A few designer issues 

Thanks Palli,

This will be a good reference when upgrading to newer VWG version.
I read a post about having technical FAQ. These steps is one of the those FAQ thing since these problems were reported before.

Anyway, I had a duplication of controls problem in designer.
I had some custom controls created, then add these custom control into user controls.

I had 3 controls with default name xxx1, xxx2, xx3. Then, after some editing the controls properties, add code behind, removed xx3 controls and add another one, tinker with new xxx3's code behind. When I'm done,  I realised in the designer.vb file it has xxx1, xxx2, xxx3, xxx4, xxx5. Those earlier xxx1 and xxx2 controls, has become xxx4 and xxx5. And xxx3 still xxx3. All previous xxx1 and xxx2 code behind now, no longer has its related controls in the designer view (they are now xxx4 and xxx5).

Sometime deleting control, its declaration is left in the designer.vb (previous post), but I didn't realise the existing control was swapped to new controls. I don't seem to be able to reproduce this error. Not sure if the default name has something to do with this. Has anyone experienced this before?
 

 
New Post 4/1/2009 7:21 PM
  jayhobbs
1351 posts
1st Level Poster




Re: A few designer issues 

Hi

Duplicated controls is a known problem.

I find it is better not to use the default name IE use PB1 instead of PictureBox1

It makes it far easier to find problems

Jay

 

 
Previous Previous
 
Next Next
  Forum  General Visual ...  Let's Chat Abou...  A few designer issues
Most promising startups
Top 3 most promising startups in 2009
   AJAX Framework | Web Development | Cloud applications | RIA Development | Silverlight Applications | Legacy Migration
The most popular open source Ajax applications framework for enterprises | Sitemap | Terms Of Use | Privacy Statement
Copyright © 2005-2009 Visual WebGui®    Design By: Template World
   
Visual Studio Partners