Designer not showing inherited forms

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have a problem that occurs does NOT occur when my laptop is connected to
the network at work.

I inherit a form from a base form. When not connected to the network, if I
try to design the inherrited from, the designer says:
"The designer could not be shown for this file because none of the classes
within it can be designed... ensure the assembly has been referenced or built
as part of the project."

When connected to the network the inherrited form is displayed by the
designer.

In investigating the problem I noticed a probably related problem. When not
connected to the network, if a use the wizard to created an inherrited form,
the wizard cannot find any of the existing forms to inherit from.

Can anyone make any suggestions to help me find out what is causing these
problems?

thanks
 
Hi Phran,

Thanks for your post!

Do you use VS.net2003 or VS2005?

With the current information you provided, it is hard for us to reproduce
out on our side. I recommended you to do tests below:
1. Create a new sample project and use inherited form, does the problem
still exist?
2. If you move this project on another machine and open it there, does the
problem still exist?

With these 2 tests, we can determine if this problem is project specific or
machine specific.

Additionally, is it possible for you to provide a reproduce project or
steps to help us reproduce the problem?

Thanks

Best regards,
Jeffrey Tan
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
 
Thanks very much for showing an interest in my problem.
Do you use VS.net2003 or VS2005? VS.net2003

With the current information you provided, it is hard for us to reproduce
out on our side. I recommended you to do tests below:
1. Create a new sample project and use inherited form, does the problem
still exist?
Click to expand...
Yes - but only when my machine is not connected to the network.
2. If you move this project on another machine and open it there, does the
problem still exist?
Click to expand...
NO - but that machine is connected to the network.
With these 2 tests, we can determine if this problem is project specific or
machine specific.

Additionally, is it possible for you to provide a reproduce project or
steps to help us reproduce the problem?
Click to expand...
When I encountered the problem I followed the steps below.

http://msdn.microsoft.com/library/d...walkthroughdemonstratingvisualinheritance.asp

At step 3 of: To add an inherited form
When disconnected from the network there is no forms to inherit from.
When connected I can complete the walkthrough. However, if I open the
project when disconnected the desigher cannot display the inheritted form.

(I do not dicount the possibility of user error :) )
 
Hi Phran,

Thanks for your feedback.

Your feedback information is really helpful.
NO - but that machine is connected to the network.
Click to expand...

Can you please disconnect that machine from the network and try to open the
designer of your project? Does the problem exist?

If this can not be reproduced, we can determine that the problem should be
your machine-specific.
When connected I can complete the walkthrough. However, if I open the
project when disconnected the desigher cannot display the inheritted form.
Click to expand...
Can you first add the inherited form with network connected and then
provide the sample project to me? I will try to open the project designer
with network disconnected.

You can add this sample project as an attachment in a further reply with
Oulook Express.

Thanks

Best regards,
Jeffrey Tan
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
 
Hi, I have managed to fix the problem. But the fix leads to questions that I
and others may find useful. This is how I did it....

I thought I would see if .net 2005 would make the problem go away. So I
installed .net 2005 at home while not connected to the network. The
installation failed because it was trying to access a h: drive.

When connected at work I have severals drives mapped including a H:. When
disconnected I don't. So I created (using subst) a H: drive and ,net 2005
installed. I wondered if the same thing was causing the inherrited form
problem. Sure enough with a h: drive I can see the form in the designer -
without one I can't.

The question now is why I need a h: drive. Is there some environment
variable for temporary files? Any ideas?
 
Hi Phran,

Thanks for your feedback.

I have some 2 suggesions regarding your issue:
1. You can use process explorer from sysinternal site to view all the
environment variables of VS2005 process. Any environment variable
containing "h:" drive will be the potential problem factor.
2. You can use file monitor from sysinternal site to monitor VS2005
process. We should take care of any file path contaning "h:\", then we can
get the detailed information regarding which file/foler the VS2005 is
trying to access.

Hope this helps!

Best regards,
Jeffrey Tan
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
 
Back
Top