vb.net 2003's library is not registered

Can anyone offer a suggestion to a following error.  Occurs upon launching of the windows application built with vb.net 2003?  "The referenced component 'FPLACELib' could not be found. Could not load the type library. Library not registered."
thank you
LVL 1
systems_axAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
SStoryConnect With a Mentor Commented:
http://msdn2.microsoft.com/en-us/library/zeaxheha(VS.80).aspx
tells that tlbimp.exe basically makes a COM wrapper so that .NET can use a COM library.

http://msdn2.microsoft.com/en-us/library/aa140210(office.10).aspx
mentions fplace.dll

is this an Office or Maps application?  Are you doin smart tags with it or something?

Have you tried repair or reinstall of vs 2003?
0
 
SStoryCommented:
Do you have such a library on the machine?  Is it a dll?  if so is it referenced in your Project properties?

Is it a com DLL? If it is, maybe regsvr32.exe the DLL to register it. If not, your project expects the file and it apparently isn't there.
0
 
systems_axAuthor Commented:
SStory,
FPLACELib is referenced under my References within the solution explorer.  It just says "FPLACELib".  When I select it and click properties, this is what says under Identity: {A57C2DAD-E30A-42F1-8A8F-8B949A06F1B0}\2.0\0\tlbimp.  I do not know if it is a com dll.
This error came out of nowhere upon a launching of the program.

I will try running regsvr32.exe.
0
Never miss a deadline with monday.com

The revolutionary project management tool is here!   Plan visually with a single glance and make sure your projects get done.

 
systems_axAuthor Commented:
just ran regsvr32.exe and it is still not registered.
0
 
systems_axAuthor Commented:
I finally decided to remove this reference and the error went away.
0
 
SStoryCommented:
Well yeah, if you stop referencing a dll that isn't there it will stop complaining.  The orignal question was what did you need the DLL for.  I said that it wasn't anything I recognized or found by googling or by searching MSDN.  I assumed it must have been some DLL specific to your application and you wanted it to work.

If there is functionality inside of that DLL that you need, then you haven't really solved the problem...you just got rid of the complaints. If you never needed it, then this was the obvious solution from the beginning.

Glad it works now.
0
 
systems_axAuthor Commented:
i am thinking that i included this reference on accident, saw a definition of it on your suggested site, thanks for your help.
0
 
systems_axAuthor Commented:
SStory,
i will assign you the points for your suggestions.
0
 
SStoryCommented:
Thanks for the points. I have no idea what that DLL does.  If you don't need a library, not referencing it is good.  I think dot net is smart enough to only include the code it needs, yet, that reference, might say, this DLL is required and if so...that would be a waste if not used.
0
All Courses

From novice to tech pro — start learning today.