Search:
Namespaces
Discussions
.NET v1.1
Feedback
legacy com objects
Messages
Related Types
This message was discovered on
ASPFriends.com 'aspngmigrate' list
.
Responses highlighted in red are from those people who are likely to be able to contribute good, authoratitive information to this discussion. They include Microsoft employees, MVP's and others who IMHO contribute well to these kinds of discussions.
Johan Myburgh
-- Moved from [aspnotnewbie] to [aspngmigrate] by
Click here to reveal e-mail address
--Hi all,=20=20Forgive me if this has already been answered.I'm referencing a legacy component in VS.NET and use it to run ASPX codeunder IIS.From time to time the component gets updated with new members and =methodsbut my assembly does not reflect those changes if I replace the old DLL.In fact VS.NET shows an error on the referenced component in the projectbrowser.In VS I can de-reference the object, reference it again and the code =willwork but what happens to the assembly after I have deployed it and I =replacethe DLL on the live server?Is there a command line utility I can use to update the .NET assembly torebuild the "wrapper" .NET creates for the legacy component?Thanx in advance...=20Johan MyburghInobits Consulting=20+27 11 478 2607 <T>+27 11 478 2623 <F>
Click here to reveal e-mail address
<Mail>
http://www.inobits.com
<Url>=20
Reply to this message...
Dan Green (VIP)
[Original message clipped]
Yep: tlbimp.exe
Dan Green
[
http://dotnetdan.com
-- putting the dan in .net ]
Reply to this message...
Ad
MBR BootFX
Best-of-breed application framework for .NET projects, developed by Matthew Baxter-Reynolds and MBR IT
Copyright © Matthew Baxter-Reynolds 2001-2008. '.NET 247 Software Development Services' is a trading style of MBR IT Solutions Ltd.
Contact Us
-
Terms of Use
-
Privacy Policy
-
www.dotnet247.com