By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
455,033 Members | 1,285 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 455,033 IT Pros & Developers. It's quick & easy.

registration of .net dll during setup

P: n/a
i have a class library in one project representing an object model. i have a
second windows application project that references the object model project.
i finally have a setup application that includes all three. the setup build
creates the om dll and the windows app exe and redistributes them as
expected. however, i suspect the reason i keep getting errors when trying to
run the app on a newly targeted pc is that the om dll isn't being registered
properly. i performed a regsvr32 on the dll directly and it reports that it
cannot find an entry-point.

is there something i need to do to the om project to define an entry-point
or is there additional steps needed to tell the setup package how to
register it or make it otherwise available to use?

tia,

steve
Nov 21 '05 #1
Share this Question
Share on Google+
9 Replies


P: n/a
"steve" schrieb
i have a class library in one project representing an object model. i have
a
second windows application project that references the object model
project.
i finally have a setup application that includes all three. the setup
build
creates the om dll and the windows app exe and redistributes them as
expected. however, i suspect the reason i keep getting errors when trying
to
run the app on a newly targeted pc is that the om dll isn't being
registered
properly. i performed a regsvr32 on the dll directly and it reports that
it
cannot find an entry-point.

is there something i need to do to the om project to define an entry-point
or is there additional steps needed to tell the setup package how to
register it or make it otherwise available to use?


Hi Steve,

..NET-Assemblies don't have to be registered in the registry. regsvr32
doesn't work with .NET-Assemblies.

If you want to share assemblies then use the Global Assembly Cache (GAC)
instead:
http://msdn.microsoft.com/library/en...emblyCache.asp

Or simply copy the dependent Class-Library into the App.exe's folder.Read
this:
http://msdn.microsoft.com/library/en...delessform.asp

Cheers

Arne Janning


Nov 21 '05 #2

P: n/a
Hi,

In additon to Arne's comments. You can use regasm.exe to register a
dot net dll for interop with a com object.

http://msdn.microsoft.com/library/de...lRegasmexe.asp

Ken
------------------
"steve" <a@b.com> wrote in message
news:10*************@corp.supernews.com...
i have a class library in one project representing an object model. i have a
second windows application project that references the object model project.
i finally have a setup application that includes all three. the setup build
creates the om dll and the windows app exe and redistributes them as
expected. however, i suspect the reason i keep getting errors when trying to
run the app on a newly targeted pc is that the om dll isn't being registered
properly. i performed a regsvr32 on the dll directly and it reports that it
cannot find an entry-point.

is there something i need to do to the om project to define an entry-point
or is there additional steps needed to tell the setup package how to
register it or make it otherwise available to use?

tia,

steve

Nov 21 '05 #3

P: n/a
| Or simply copy the dependent Class-Library into the App.exe's folder.Read
| this:
|
http://msdn.microsoft.com/library/en...delessform.asp
|
thx for the info, arne. the first link had, and led to, a lot of other
useful info.
the above link talked about model/less forms. anyway, the dll does reside in
the same folder as the application's exe. i'd prefer this approach but my
app is blowing up when run (doesn't even show the first form which is a
static splash-screen). we had tested a previous version successfully on the
new pc. the only difference between that version and this is that we gave
the om its own namespace and put it in a project of its own. that seems to
be where the problem lies.

any other ideas?
Nov 21 '05 #4

P: n/a
"steve" schrieb
| Or simply copy the dependent Class-Library into the App.exe's folder.Read
| this:
|
http://msdn.microsoft.com/library/en...delessform.asp
Sorry,

I was preparing several posts to several questions and copied the wrong url.
The link I meant is:
http://msdn.microsoft.com/library/en...sualStudio.asp
thx for the info, arne. the first link had, and led to, a lot of other
useful info.
the above link talked about model/less forms. anyway, the dll does reside
in
the same folder as the application's exe. i'd prefer this approach but my
app is blowing up when run (doesn't even show the first form which is a
static splash-screen). we had tested a previous version successfully on
the
new pc. the only difference between that version and this is that we gave
the om its own namespace and put it in a project of its own. that seems to
be where the problem lies.


Any error messages?

Would be useful.

Cheers

Arne Janning
Nov 21 '05 #5

P: n/a
this is what displays in the dialog box (title = common language runtime
debugging services)

==================

application has generated an exception that could not be handled.

process id=0xe98(3736), thread id=0xb04(2820).

click ok to terminate the application.
click cancel to debug the application

==================

it is a new win2k3 server and has no debugger installed...so clicking cancel
is futile.

thanks for your help!
Nov 21 '05 #6

P: n/a
Yeah.. did you reference that project when you changed the namespace? That
can cause a problem... or it wouldn't compile. your post is a little
confusing.
"steve" <a@b.com> wrote in message
news:10*************@corp.supernews.com...
| Or simply copy the dependent Class-Library into the App.exe's folder.Read | this:
|
http://msdn.microsoft.com/library/en...delessform.asp |
thx for the info, arne. the first link had, and led to, a lot of other
useful info.
the above link talked about model/less forms. anyway, the dll does reside in the same folder as the application's exe. i'd prefer this approach but my
app is blowing up when run (doesn't even show the first form which is a
static splash-screen). we had tested a previous version successfully on the new pc. the only difference between that version and this is that we gave
the om its own namespace and put it in a project of its own. that seems to
be where the problem lies.

any other ideas?

Nov 21 '05 #7

P: n/a
sorry about the confusion.

| did you reference that project when you changed the namespace?

yes -

"i have a class library in one project representing an object model. i have
a
second windows application project that references the object model project.
i finally have a setup application that includes all three."

the object model compile to a dll. the windows application references the om
project. after install, the dll is in the windows application root
directory.

where am i going wrong or what else would cause the problem?
Nov 21 '05 #8

P: n/a
"steve" schrieb
sorry about the confusion.

| did you reference that project when you changed the namespace?

yes -

"i have a class library in one project representing an object model. i
have
a
second windows application project that references the object model
project.
i finally have a setup application that includes all three."

the object model compile to a dll. the windows application references the
om
project. after install, the dll is in the windows application root
directory.

where am i going wrong or what else would cause the problem?


Sorry Steve,

deploying .NET-Assemblies normally is not a big problem.

If it is not a problem for you, send the complete solution off the list and
I'll fix it for you.

Cheers

Arne Janning

Nov 21 '05 #9

P: n/a
thanks for your willingness to look at it. do you have windows 2003 server
to test it on...the problem only occurs on that os.

if so, just respond that your email adress is infact
ta******************@msn.com and i'll zip it and email it. you'll also need
msde running...db and create table scripts are inclusive.

thanks again,

me
"Arne Janning" <sp*****************@msn.com> wrote in message
news:eg**************@TK2MSFTNGP15.phx.gbl...
| "steve" schrieb
| > sorry about the confusion.
| >
| > | did you reference that project when you changed the namespace?
| >
| > yes -
| >
| > "i have a class library in one project representing an object model. i
| > have
| > a
| > second windows application project that references the object model
| > project.
| > i finally have a setup application that includes all three."
| >
| > the object model compile to a dll. the windows application references
the
| > om
| > project. after install, the dll is in the windows application root
| > directory.
| >
| > where am i going wrong or what else would cause the problem?
|
| Sorry Steve,
|
| deploying .NET-Assemblies normally is not a big problem.
|
| If it is not a problem for you, send the complete solution off the list
and
| I'll fix it for you.
|
| Cheers
|
| Arne Janning
|
|
|
|
|
Nov 21 '05 #10

This discussion thread is closed

Replies have been disabled for this discussion.