I am upgrading a VS 2008 project to VS 2010 and have come across this issue where the DLL is referenced, but the IDE errors on anything attempting to use it. I don't have the code for the library as it comes from another source. Any tips on what I can do
to try to get this thing to be recognized?
I've checked the items suggested in the error message, but still cannot get it to work.
"Namespace or type specified in the Imports '***talCommon' doesn't contain any public member or cannot be found. Make sure the namespace or the type is defined and contains at least one public member. Make sure the imported element name doesn't use any aliases."
I can suggest a little test that *may* lead to a solution - create a new project, then try to add the problematic assembly alone. Then at the IDE check if you can access a public method.
If it works, then you probably have a extension name resolution issue.
That depends on how your application is implemented.
For instance, if it's a ASP.NET application, you may try to check the System.Web.Extensions entry at the web.config file of the new standalone application. Then copy the auto-generated content from there to the application you`re working at.
KJAK
Participant
1673 Points
478 Posts
Upgrading .NET Issues
Oct 04, 2012 01:27 PM|LINK
I am upgrading a VS 2008 project to VS 2010 and have come across this issue where the DLL is referenced, but the IDE errors on anything attempting to use it. I don't have the code for the library as it comes from another source. Any tips on what I can do to try to get this thing to be recognized?
I've checked the items suggested in the error message, but still cannot get it to work.
"Namespace or type specified in the Imports '***talCommon' doesn't contain any public member or cannot be found. Make sure the namespace or the type is defined and contains at least one public member. Make sure the imported element name doesn't use any aliases."
KJAK
OnoSendai
Participant
1144 Points
239 Posts
Re: Upgrading .NET Issues
Oct 04, 2012 01:55 PM|LINK
I can suggest a little test that *may* lead to a solution - create a new project, then try to add the problematic assembly alone. Then at the IDE check if you can access a public method.
If it works, then you probably have a extension name resolution issue.
KJAK
Participant
1673 Points
478 Posts
Re: Upgrading .NET Issues
Oct 04, 2012 02:14 PM|LINK
It worked in a stand-alone application. Please explain how to resolve the extension name resolution issue?
KJAK
OnoSendai
Participant
1144 Points
239 Posts
Re: Upgrading .NET Issues
Oct 04, 2012 02:21 PM|LINK
That depends on how your application is implemented.
For instance, if it's a ASP.NET application, you may try to check the System.Web.Extensions entry at the web.config file of the new standalone application. Then copy the auto-generated content from there to the application you`re working at.
And let us know if it works ;)