Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / Languages / C# / July 2007

Tip: Looking for answers? Try searching our database.

AddIn Problem

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Rainer Queck - 10 Jul 2007 10:05 GMT
Hello NG,

I moved my AddIn Project from one machine to a other.

This AddIn is a AddIn for Visual Studio 2005.

Now I cant test it any more. It builds Ok and starting the debugger an other
instance of VS2005 is started also, but my AddIn doesn't show in the Tools
Menu.

I suppose, there is a certain procedure to follow, if a AddIn Project is
moved from one machine to a other, right? If so, what is the right way?

Also, how can I deploy a AddIn? Which files must be placed where?

Thanks for any help!

Regards

Rainer Queck
Walter Wang [MSFT] - 11 Jul 2007 03:55 GMT
Hi Rainer,

There should be a linked file such as "MyAddin123 - For Testing.AddIn" in
the project which points to a path such as "E:\Documents and
Settings\wawang\My Documents\Visual Studio 2005\Addins\MyAddin123 - For
Testing.AddIn", the content of this file will point to current project's
generated assembly, therefore when the second instance of IDE starts up, it
will load it.

I think you need to copy this file from your original machine and copy to
new machine, also you need to modify the path to the addin assembly.

Hope this helps. Please feel free to let me know if there's anything
unclear. Thanks.

Regards,
Walter Wang (wawang@online.microsoft.com, remove 'online.')
Microsoft Online Community Support

==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================

This posting is provided "AS IS" with no warranties, and confers no rights.
Rainer Queck - 11 Jul 2007 10:30 GMT
Hi Walter,

> Hope this helps. Please feel free to let me know if there's anything
> unclear. Thanks.
Yes, that helped. I can now continue the work on my add-in on my new
machine. Thanks!

Regards
Rainer
Peter Macej - 11 Jul 2007 10:00 GMT
> Also, how can I deploy a AddIn? Which files must be placed where?

The add-in must be registered on target machine. See
http://www.mztools.com/articles/2007/MZ009.htm for the most common
problems, including yours.

Also, see this great series of articles about VS add-ins from Carlos J.
Quintero - http://www.mztools.com/resources_vsnet_addins.htm. You will
find almost everything you need to know when creating VS add-in there.

Signature

Peter Macej
Helixoft - http://www.helixoft.com
VSdocman - Commenter and generator of class documentation for C#, VB
.NET and ASP .NET code

Rainer Queck - 11 Jul 2007 10:36 GMT
Hello Peter,

thank you very much for those links.
Looks like I can gather lots of information there.
I think I start reading right now ;-)

Regards
Rainer

>> Also, how can I deploy a AddIn? Which files must be placed where?
>
[quoted text clipped - 5 lines]
> Quintero - http://www.mztools.com/resources_vsnet_addins.htm. You will
> find almost everything you need to know when creating VS add-in there.

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.