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

Does VB.NET provide the way to deploy library to internal developer?

P: n/a
meo
Does .NET provide the way to deploy library to internal developer?

I am trying to find the way to deploy a library file to developer for having
integration to their application BUT the customer who is using that
application will not use that library file.

If I choose to deploy like a DLL file, the DLL file will deploy to the
customer. I thought this is the easy way if customer copy DLL file to
include to the project and use it.

BUT I choose to deploy like a sourcecode, it is hard to control version and
policy.

The past on C++, we have file .LIB to handle this case. but from now what we
can do.

PS: Someone told me to use utility tlbexp.exe to export .DLL to .TLB, but I
cannot include .TLB which is generated from the .DLL to the project by
adding reference.
May 24 '07 #1
Share this Question
Share on Google+
4 Replies


P: n/a
On May 23, 11:37 pm, "meo" <j_ala...@hotmail.comwrote:
Does .NET provide the way to deploy library to internal developer?

I am trying to find the way to deploy a library file to developer for having
integration to their application BUT the customer who is using that
application will not use that library file.

If I choose to deploy like a DLL file, the DLL file will deploy to the
customer. I thought this is the easy way if customer copy DLL file to
include to the project and use it.

BUT I choose to deploy like a sourcecode, it is hard to control version and
policy.

The past on C++, we have file .LIB to handle this case. but from now what we
can do.

PS: Someone told me to use utility tlbexp.exe to export .DLL to .TLB, but I
cannot include .TLB which is generated from the .DLL to the project by
adding reference.
About the closest thing I can think of is a netmodule. You can't
create it from the ide, but you can compile one from the command
line. Then the other developer can link it into his assembly - again,
a command line process.

Just a thought.

--
Tom Shelton

May 24 '07 #2

P: n/a
meo
Pls let me know more.

Can the other developer bring the assembly to integrate to their application
vua IDE?

"Tom Shelton" <to*********@comcast.netwrote in message
news:11**********************@b40g2000prd.googlegr oups.com...
On May 23, 11:37 pm, "meo" <j_ala...@hotmail.comwrote:
>Does .NET provide the way to deploy library to internal developer?

I am trying to find the way to deploy a library file to developer for
having
integration to their application BUT the customer who is using that
application will not use that library file.

If I choose to deploy like a DLL file, the DLL file will deploy to the
customer. I thought this is the easy way if customer copy DLL file to
include to the project and use it.

BUT I choose to deploy like a sourcecode, it is hard to control version
and
policy.

The past on C++, we have file .LIB to handle this case. but from now what
we
can do.

PS: Someone told me to use utility tlbexp.exe to export .DLL to .TLB, but
I
cannot include .TLB which is generated from the .DLL to the project by
adding reference.

About the closest thing I can think of is a netmodule. You can't
create it from the ide, but you can compile one from the command
line. Then the other developer can link it into his assembly - again,
a command line process.

Just a thought.

--
Tom Shelton

May 24 '07 #3

P: n/a
AFAIK not directly but as the build process in 2005 is customizable you
could perhaps add this... See the /target:module option
(http://msdn2.microsoft.com/en-us/lib...hx(VS.80).aspx) of the
command line compiler.

Another option would be to build something in your application to prevent
this (for example it looks like a licensing scheme). Google comes with
things such as http://www.developer.com/net/net/article.php/3074001
"meo" <j_******@hotmail.coma écrit dans le message de news:
eA**************@TK2MSFTNGP02.phx.gbl...
Pls let me know more.

Can the other developer bring the assembly to integrate to their
application vua IDE?

"Tom Shelton" <to*********@comcast.netwrote in message
news:11**********************@b40g2000prd.googlegr oups.com...
>On May 23, 11:37 pm, "meo" <j_ala...@hotmail.comwrote:
>>Does .NET provide the way to deploy library to internal developer?

I am trying to find the way to deploy a library file to developer for
having
integration to their application BUT the customer who is using that
application will not use that library file.

If I choose to deploy like a DLL file, the DLL file will deploy to the
customer. I thought this is the easy way if customer copy DLL file to
include to the project and use it.

BUT I choose to deploy like a sourcecode, it is hard to control version
and
policy.

The past on C++, we have file .LIB to handle this case. but from now
what we
can do.

PS: Someone told me to use utility tlbexp.exe to export .DLL to .TLB,
but I
cannot include .TLB which is generated from the .DLL to the project by
adding reference.

About the closest thing I can think of is a netmodule. You can't
create it from the ide, but you can compile one from the command
line. Then the other developer can link it into his assembly - again,
a command line process.

Just a thought.

--
Tom Shelton


May 24 '07 #4

P: n/a
meo
I see that when I'm using /target:module to compile my sourcecode as a
library. This is work fine.

BUT for using to integrate library with the application, the application has
to use command line to compile too. This cannot be adding library to IDE of
Visual Studio to compile. Do I make something miss?

I thought the solution is work if I can compile *.vb by using commandline
and integrate to the application by using IDE. BUT it is not work if I have
to integrate library to application by using commandline.
"Patrice" <http://www.chez.com/scribe/wrote in message
news:%2****************@TK2MSFTNGP03.phx.gbl...
AFAIK not directly but as the build process in 2005 is customizable you
could perhaps add this... See the /target:module option
(http://msdn2.microsoft.com/en-us/lib...hx(VS.80).aspx) of the
command line compiler.

Another option would be to build something in your application to prevent
this (for example it looks like a licensing scheme). Google comes with
things such as http://www.developer.com/net/net/article.php/3074001
"meo" <j_******@hotmail.coma écrit dans le message de news:
eA**************@TK2MSFTNGP02.phx.gbl...
>Pls let me know more.

Can the other developer bring the assembly to integrate to their
application vua IDE?

"Tom Shelton" <to*********@comcast.netwrote in message
news:11**********************@b40g2000prd.googleg roups.com...
>>On May 23, 11:37 pm, "meo" <j_ala...@hotmail.comwrote:
Does .NET provide the way to deploy library to internal developer?

I am trying to find the way to deploy a library file to developer for
having
integration to their application BUT the customer who is using that
application will not use that library file.

If I choose to deploy like a DLL file, the DLL file will deploy to the
customer. I thought this is the easy way if customer copy DLL file to
include to the project and use it.

BUT I choose to deploy like a sourcecode, it is hard to control version
and
policy.

The past on C++, we have file .LIB to handle this case. but from now
what we
can do.

PS: Someone told me to use utility tlbexp.exe to export .DLL to .TLB,
but I
cannot include .TLB which is generated from the .DLL to the project by
adding reference.

About the closest thing I can think of is a netmodule. You can't
create it from the ide, but you can compile one from the command
line. Then the other developer can link it into his assembly - again,
a command line process.

Just a thought.

--
Tom Shelton



May 24 '07 #5

This discussion thread is closed

Replies have been disabled for this discussion.