Designer issues

  • Thread starter Thread starter Nicholas Paldino [.NET/C# MVP]
  • Start date Start date
N

Nicholas Paldino [.NET/C# MVP]

Alvin,

If you could describe how exactly it messes up, then it would help. Can
you provide a complete example which displays the problem?
 
Why is it that when I move a form (.cs and .resx) file in a project to a sub
folder it totally flucks up on the apps using that component.

No code changes just the actual project structure for the control.

The designer has serious issues.

I regard it as work in progress, not final.
 
Hi Alvin

I haven't tried, but I guess that this is because the resx files goes as a
resource in the assembly. If you move the resource file the name of the
subfolder becomes part of the resource full name and then the form can't
load it.

B\rgds
100
 
So where do we fix this, and why cant the designer do this refactoring for
us since in 2004 it looks like refactoring (POGO) etc is all the rage.
 
* "Alvin Bruney said:
Why is it that when I move a form (.cs and .resx) file in a project to a sub
folder it totally flucks up on the apps using that component.

No code changes just the actual project structure for the control.

The designer has serious issues.
Click to expand...

I am not able to repro that in VB.NET 2003 or C# 2003.
Which problems occur after moving the file?
 
Resource culture crap messages when you try to run the app and invisible
controls.
 
That what it says when cannot load the resource. You can get the same if you
declare something before the control class. The control class has to be the
first thing declared in the file.

Alvin Bruney said:
Resource culture crap messages when you try to run the app and invisible
controls.


a
Click to expand...
 
Nothing was edited in the code, just moved into a subfolder that the IDE
knew about.

So, what must be changed in the resx file then

100 said:
That what it says when cannot load the resource. You can get the same if you
declare something before the control class. The control class has to be the
first thing declared in the file.

Alvin Bruney said:
Resource culture crap messages when you try to run the app and invisible
controls.
Click to expand...
to
Click to expand...
 
I think it can't handle it. How I said before, this is because it changes
the name of the resource in the assembly metadata. It is just a guess,
though.
Look with ILDasm in the assembly to see the name of the embeded resource.
But you can't do anything, I think.
 
Its stupid then, how hard is it to refactor code on visual studio, bloody
difficult with resx fiels then.

The project is just text, whats so hard to change. there is no binary in a
project.

so I lose all my checkin changes if i move a form to a diff location on a
project? What are they on, crack?
 
* "Alvin Bruney said:
Its stupid then, how hard is it to refactor code on visual studio, bloody
difficult with resx fiels then.

The project is just text, whats so hard to change. there is no binary in a
project.

so I lose all my checkin changes if i move a form to a diff location on a
project? What are they on, crack?
Click to expand...

Are you using VS.NET 2003?
 
Back
Top