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

.NET assembly : strongly named

P: n/a
I have a .NET DLL that uses ADO 2.8 DLL.
I am not able to "strongly name" the .NET DLL.

Any comments, work arounds ?

CHDe

---
Posted using Wimdows.net NntpNews Component -

Post Made from http://www.DotNetJunkies.com/newsgroups Our newsgroup engine supports Post Alerts, Ratings, and Searching.
Nov 20 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
"DotNetJunkies User" <User@-NOSPAM-DotNetJunkies.com> wrote in message
news:eZ**************@tk2msftngp13.phx.gbl...
I have a .NET DLL that uses ADO 2.8 DLL.
I am not able to "strongly name" the .NET DLL.


Look into the tlbimp utility - this allows you to create a "Primary
Interop Assembly" from the ADO assembly and Strongly Name it,
which will then allow you Strongly Name your own assembly.

Do you absolutely /have/ to use ADO 2.8? IIRC, Our Friends
in Redmond already provide a P.I.A. for ADO 2.7.

HTH,
Phill W.
Nov 20 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.