ANOTHER POST TO MICROSOFT TO SOLVE DESIGNER BUG ASAP !!!!

  • Thread starter Thread starter João Santa Bárbara
  • Start date Start date
J

João Santa Bárbara

Hi all,

Once again lots of people who have migrate from previous .NET version is
facing lots of problems with VSNET 2005 form designer. I´m Not an exception.
This post is to ask to Microsoft when is going to be relased the fix for
this bug. I supose for what i have searched in the Internet, that Microsoft
does not have a way to reproduce the problem. Here is a thought, try to
migrate all you work to VS 2005 and let the people know what happen.
perhaps the same problem occurs ..

I already create a new solution, and 3 new projects, from scratchs native
VS.2005, and i import all my forms and controls from the older projects and
the problems continues.

This bug occurs when i have 3 projects envolved ( in my case )

i have in the 1º project a few user controls ( mine )
in the 2 project i have a base form with those controls
and in the 3 project i have an inherited form ( derived from project 2
forms )
all projects are referenced all projects have random version, i allready
try to set a fixed version and its the same thing


thks to all
JSB

PS: i´m tired to close VS.NET and to open again several times a day

Here it goes the bug

Unable to load one or more of the requested types. Retrieve the
LoaderExceptions property for more information.
Hide

at System.Reflection.Module.GetTypesInternal(StackCrawlMark&
stackMark)
at System.Reflection.Assembly.GetTypes()
at
Microsoft.VisualStudio.Shell.Design.AssemblyObsoleteEventArgs..ctor(Assembly
assembly)
at
Microsoft.VisualStudio.Design.VSDynamicTypeService.ReloadAssemblyIfChanged(String
codeBase)
at
Microsoft.VisualStudio.Design.VSDynamicTypeService.CreateDynamicAssembly(String
codeBase)
at
Microsoft.VisualStudio.Design.VSTypeResolutionService.AssemblyEntry.get_Assembly()
at
Microsoft.VisualStudio.Design.VSTypeResolutionService.AssemblyEntry.Search(String
fullName, String typeName, Boolean ignoreTypeCase, Assembly& assembly,
String description)
at
Microsoft.VisualStudio.Design.VSTypeResolutionService.SearchProjectEntries(AssemblyName
assemblyName, String typeName, Boolean ignoreTypeCase, Assembly& assembly)
at
Microsoft.VisualStudio.Design.VSTypeResolutionService.GetType(String
typeName, Boolean throwOnError, Boolean ignoreCase, ReferenceType refType)
at
Microsoft.VisualStudio.Design.Serialization.CodeDom.AggregateTypeResolutionService.GetType(String
name, Boolean throwOnError, Boolean ignoreCase)
at
Microsoft.VisualStudio.Design.Serialization.CodeDom.AggregateTypeResolutionService.GetType(String
name)
at
System.ComponentModel.Design.DesignerHost.System.ComponentModel.Design.IDesignerHost.GetType(String
typeName)
at
System.ComponentModel.Design.Serialization.CodeDomDesignerLoader.EnsureDocument(IDesignerSerializationManager
manager)
at
System.ComponentModel.Design.Serialization.CodeDomDesignerLoader.PerformLoad(IDesignerSerializationManager
manager)
at
Microsoft.VisualStudio.Design.Serialization.CodeDom.VSCodeDomDesignerLoader.PerformLoad(IDesignerSerializationManager
serializationManager)
at
System.ComponentModel.Design.Serialization.BasicDesignerLoader.BeginLoad(IDesignerLoaderHost
host)
 
I have been having a few problems with the UI designer on some of my
converted vs 2003 projects.
Simply put, on occasions (around 50% of the time) when I try and open a form
in the UI designer, it won't render but will display an error message where
the UI should be. The error message can be pretty random.

In my case I have found that closing the form, then right clicking the
solution node in solution explorer and selecting 'rebuild' usually fixes the
issue (until the next time). This stops me having to restart VS.net around
20 times a day.

There's nothing really special about these projects, some windows forms with
custom UserControls (from the second project in my solution).
I have noticed that vs.net attempts to set some properties automatically on
some third party controls and that occasionally creates the above error.
For example, I have a third party checkbox control on one of my forms. When
I open the form, it will refuse to render and my task list will show the
error 'checkbox1.image is read only'. The UI designer has attempted to
automatically add 'checkbox1.image = nothing' to the display code. Once I
strip it out and rebuild, it is fine - until the next time I open the form
and VS.net will automatically put that line in again!! The same thing
happens with a few other controls that worked perfectly well in vs.net 2003.
Annoying - you bet!

I'm slowly stripping out the third party controls that the UI appears to
have a problem with, but I gotta say, this is very annoying indeed. I feel
like there are definately some bugs in there with the UI designer that
should be addressed.

Richard.
 
João Santa Bárbara said:
This post is to ask to Microsoft when is going to be relased the fix for
this bug. I supose for what i have searched in the Internet, that Microsoft
Click to expand...

<snip long bug description>

This is not the proper place to register a bug report. If you want
Microsoft to see this, you need to post it in the proper place. Here
is the link for Microsoft bug reporting:

http://lab.msdn.microsoft.com/productfeedback/
 
Yes, in fact you can report these bugs right through the IDE.

João Santa Bárbara said:
This post is to ask to Microsoft when is going to be relased the fix for
this bug. I supose for what i have searched in the Internet, that
Microsoft
Click to expand...

<snip long bug description>

This is not the proper place to register a bug report. If you want
Microsoft to see this, you need to post it in the proper place. Here
is the link for Microsoft bug reporting:

http://lab.msdn.microsoft.com/productfeedback/
 
Yes Thanks i know, but this bug is already reported, and closed but no fix
....

mean while all people who have this bug continues to work everyday and
continue to restart the VS.NET e few times a day, and this is not an option
that most companys can live with. it ....


JSB
 
I tried posting my visual studio 2005 tools for office bug there, all i can
say is after a week still no response, makes you wonder if they are busy
fixing lots of issues, maybe they shouldnt have released.
 
This is NOT a bug!

You and Richard are referencing items in controls that do not reside either
in a resource or in their original directory location or some other missing
reference in your UI. This happens to me and in all cases it is due to a
bad reference.

Now, I agree that VS 2005 does NOT handle the problem very well (in fact
pretty poorly) -- as the only work around I know is to figure out what the
reference was and put it in the expected locaiton/dir.

Rob.
 
I tried posting my visual studio 2005 tools for office bug there, all i can
say is after a week still no response, makes you wonder if they are busy
fixing lots of issues, maybe they shouldnt have released.
Click to expand...

In fact, there is a lot of activity in the bugs you file. You don't see it
reflected on the external MSDN Web site as internal information, discussions
and interaction between groups are not getting published. Also, this is
holiday time, so since fewer people are around, some issues may have to wait
until owners return after holidays.

As a matter of fact, this year we are actively fixing bugs before we proceed
with coding of the next VS so we won't enter new release cycle with the bug
debt.

Again, if issue is a major block for your business you can file a request
for the fix with the tech support. If PSS won't find a workaround, you may
get hotfix issued.

Thanks
Mikhail Arkhipov (Microsoft)
-- This post is provided 'AS IS' with no warranties and confers no rights
 
NOT a BUG ???? YOU MUST BE JOKING ...

i have all projects in the same solution, and i have put the correct
references in all projects.
and it still happens ...
" Rob R. Ainscough " YOU are joking with people who have to deal with this
problem everyday ( restarting vs.net with a project with a few classes and
objects )


I THINK that Microsoft should launch a fix pack for those things that does
not have workarrounds, and this one is one of them. I could tell you more,
like the designer is allways fliking. what a stupid thing todo...
my forms designer everytime i move or change an object or a group of objects
the mouse poiter is fliking alot, consuming machine resources (CPU 100%) and
most important keeping me to work.

this kinds of bugs are stupid, and keep the developer ocupied seraching fixs
and workarround for them

JSB
 
Not sure about João's problem, but in my case it's definately not a
reference problem, more a problem with VS.net UI designer inserting
sourcecode that shouldn't be there.

In one of my app's, I use a third party checkbox control (have since moved
back to regular checkboxes to sort the problem out). Whenever I open the
form in VS.net UI designer, perform an action and save it, it will
immediately fail. Looking in the 'errors' panel, I see that a new line of
code has been inserted in the UI design area 'chkWhatever.Image = nothing'
and VS.net's error checking complains that 'image' is readonly (which is
correct). The problem is I can remove that line, then hit rebuild to fix,
but EVERYTIME I open a form with that control on it and save the form again,
then the UI designer will automatically put that line of code back in.
I have had similar problems with other controls, where the UI designer tries
to set properties that are read only.
I'm slowly moving back to regular controls that come with vs.net, so in my
case I'm able to solve the problem, but it is highly annoying and very
confusing the firsttime you open a form and it won't render.

Richard.
 
I think you mean the bug somebody already found a work-around for in the
"User Control Designer Errors is [sic] VS2005 RC1" thread.

Change your AssemblyInfo.cs files in the UserControls DLLs as follows:
[assembly: AssemblyVersion("5.5.5")]

Where 5.5.5 is any hard-coded version number. The problem was the .* in it
causing the UserControl to have an auto-generated version that's different
than what your other DLL is expecting. As soon as you recompile it with
changes or something, you get the Unable to Load error.

BTW - Notice I called it a BUG. I truly believe it's a bug. There's a
rational explanation for what it's doing, but it is bound to cause a little
frustration for a lot of people.

Happy coding!
 
I honestly think Microsoft is a very irresponsible company for
releasing non-tested products. Its a shame that I have been trying to
migrate a pocketpc project from vs2003 to vs2005 and it seems like the
designer took a few days off. I dont know where its gone.

And besides, what is the 'Aliases' property in the PropertyGrid for the
assemblies ? Now all assemblies have the 'global' alias . Sometimes I
get bugs like: Type 'x' needs a reference to System.PocketPC.asmmeta;
When I add the reference, then it says things like: Type 'x' is in
assembly System in System.dll and System.PocketPc.asmmeta.

What on earth is this ? Please let me know. I am going insane.

Alexander German
MCP C# / VB.NET
 
I honestly think Microsoft is a very irresponsible company for
releasing non-tested products.
Click to expand...

Non-tested? I've been using the various betas for over a year.

I'm not saying that it has a few bugs, but let's stick to reality here. You
may have a point (I don't know, as I haven't seen this before); don't damage
your credibility with ridiculous statements. It weakens your position.

Here's a link to a page where you can report a bug, request a feature, etc.,
and expect to get an answer:

http://lab.msdn.microsoft.com/productfeedback/

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer
We got a sick zebra a hat,
you ultimate tuna.


Alexander German said:
I honestly think Microsoft is a very irresponsible company for
releasing non-tested products. Its a shame that I have been trying to
migrate a pocketpc project from vs2003 to vs2005 and it seems like the
designer took a few days off. I dont know where its gone.

And besides, what is the 'Aliases' property in the PropertyGrid for the
assemblies ? Now all assemblies have the 'global' alias . Sometimes I
get bugs like: Type 'x' needs a reference to System.PocketPC.asmmeta;
When I add the reference, then it says things like: Type 'x' is in
assembly System in System.dll and System.PocketPc.asmmeta.

What on earth is this ? Please let me know. I am going insane.

Alexander German
MCP C# / VB.NET





Jonathan said:
I think you mean the bug somebody already found a work-around for in the
"User Control Designer Errors is [sic] VS2005 RC1" thread.

Change your AssemblyInfo.cs files in the UserControls DLLs as follows:
[assembly: AssemblyVersion("5.5.5")]

Where 5.5.5 is any hard-coded version number. The problem was the .* in
it
causing the UserControl to have an auto-generated version that's
different
than what your other DLL is expecting. As soon as you recompile it with
changes or something, you get the Unable to Load error.

BTW - Notice I called it a BUG. I truly believe it's a bug. There's a
rational explanation for what it's doing, but it is bound to cause a
little
frustration for a lot of people.

Happy coding!
Click to expand...
Click to expand...
 
I think you need to step out of your world and realized that what you're
saying is off-base. As opposed to us simple programmers out here, Microsoft
as a whole is probably maintaining several billion lines of code. Nobody's
perfect, and I believe it's safe to say that when the number of lines of
code increases, so does the potential to have more bugs.

The example you give below is really not directly related to the base .NET
Framework. The Compact Framework has always been in flux and it seems that
Microsoft is still trying to get a grasp of what is needed. This type of
scenario is always more prone to errors because it's a moving target. I
believe that once Microsoft gets a codebase laid down for this area of
programming, then the bugs should decrease. In the mean time, all you can
really do is help by reporting these bugs and continue to look for
workarounds so as to keep yourself productive programmatically.

Microsoft is not any more irresponsible that we programmers are. With their
volume of code, we would go insane if we had to wait 5 to 10 years to get
the perfect release.
 
Back
Top