Designer not working - My.Resources.Resources' does not have a named property

I have a problem that the designer will not display forms. It does not work with an error constructor warning the following:

enter image description here

How can I fix this problem?

+8
source share
7 answers

It looks like you are missing the elements needed to load this form into the Resources application.

You can access Project Resources by right-clicking the project and selecting Properties . Then click Resources in the left pane.

Project resources

The errors you received indicate that the elements necessary for loading this form into your application, which should be downloaded from Resources , were not found. In most cases, these elements may be Images.

You might want to change the constructor code or restore missing elements in Resources .

Note Resources can be Strings , Images , Icons , Audio , Files or Others .

Thanks,
Hope you find this helpful :)

+5
source

This can happen if your project is referenced by itself .

Visual Studio randomly does this automatically when some controls / forms defined in a project use other (custom) controls defined in the same project .

You can safely remove self-esteem in the project "Links" node.

Then rebuild, and the developer should reload without these errors.

+17
source

I know this is a very old post, but people will get this error, they will find this post, and by the time they are viewed they have pulled out most of their hair, however this is what I found:

  • This is not you, this is MS. I am using VS 2015 and I am still getting this!
  • I found this to happen when some project is referencing itself
  • This is not always visible on the node links.

To solve:

  • Make clean
  • Delete BIN folder
  • FOR APPOINTMENT the link to the project displays an exe file
  • Compile
  • Close and open VS
  • Check your node link, you should see exe with a link to itself with an exclamation mark, delete the link
  • Make another build

I find that at this point my problem is resolved and I can continue to work (at least for this day)

Hope this helps people who have just become bald while using MS products!

+4
source


I used the project name xxx ".

  • Open / edit project file ( xxx .csproj or xxx .vbproj)
  • Find this xml node and delete.
    <Reference Include="xxx, Version=1.0.0.0, Culture=neutral, processorArchitecture=x86"> <ExecutableExtension>.exe</ExecutableExtension> </Reference>
  • Open and reload.
+3
source

This is an answer from Richard . I just had to make one change for obvious reasons. I want to hold my hair!

To solve:

  • AT APPOINTMENT specify projects the output file, (dll or exe)
  • Make clean
  • Delete BIN folder
  • Compile Close and Open VS
  • Unload the project and edit the project
  • Check your node link, you should see exe or ddl with a self-link with an exclamation mark, remove the link
  • Make another build
+2
source

I found that this is due to a β€œoverlap” of the namespace in which my office project located in the main solution (VB.NET) had the same root namespace as the class library (main project) on which it referred. (Did you get all this?)

For example, my main project ("MainProject") specified the root namespace of Company.Project . and my utility project (slyly called "UtilityProject") also indicated the root namespace of Company.Project .

The error can be temporarily fixed by re-adding (in my case) links to image resource sources in their properties. But as soon as the project was closed and reopened, POOF!, Left.

Since I should link to my main project in my office project, I couldn't just follow the tips elsewhere here and remove the link. So I tried to change the root namespace of the service project to Company , fixed some errors that occurred in the links of the form designer, and Bob became my uncle again.

0
source

I had the same problem when I changed the namespace. So, what I did: 1) I changed the namespace, selecting it and renaming it 2) I clicked on the light bulb and renamed all the links 3) removed all the projects from the solution 4) closed the visual studio 5) renamed all the projects in the windows explorer 6) opened visual studio and added all the projects again. The above steps I took to change the namespace, but when I opened the window form, I got the same errors as here, on the first screen that you had. To fix this, I noticed that I need to go to the properties of each project I have, and also rename the namespace. When I did this, this error was resolved, and everything worked fine again.

0
source

All Articles