looking in wrong place for DLL

[Anonymous]

I have a project in the '...\Visual Studio 2010\Projects\...'  directory and I have that path in the Addin file. But I'm getting an error about '...does not exist'. I have copied and pasted that path and DLL name into the addin file, just like I always do, but for some reason it's still looking for it in the wrong place. I started the project from a template I downloaded. This has me stumped, any ideas? Thanks.

[Anonymous]

OK, this is ridiculous. I have removed all addins from the addin folder and uninsulated and reinstalled revit. I'm still getting the error "External Tools - Add-in Assembly Not Found". I created two projects with this template. The included addin file had both Command and Application placeholders. So I'm getting four errors, a command and application error for each project. Any ideas? Thanks.

[jeremytammik]

Dear Bryan,

The only thing that can cause a Revit add-in to be loaded, or searched for to cause that message to appear, is an add-in manifest in one of the two locations checked by Revit, for all users or a specific user. These locations again depend on the OS, whether Vista or XP, so you end up with four possible locations to check. They are listed in the Revit SDK developer guide:

For Windows XP:

C:\Documents and Settings\<your login>\Application Data\Autodesk\Revit\Addins\2012

or

C:\Documents and Settings\All Users\Application Data\Autodesk\Revit\Addins\2012

For Vista/Windows 7:

C:\Users\<your login>\AppData\Roaming\Autodesk\Revit\Addins\2012

or

C:\ProgramData\Autodesk\Revit\Addins\2012

If you have deleted all files in those two directories, the error cannot appear.

If the add-in manifest was placed there by the Visual Studio Revit add-In wizard, then you can also simply open that project in Visual Studio and select Build > Clean Solution to remove it again.

Cheers, Jeremy.

--
Jeremy Tammik
Autodesk Developer Network -- http://www.autodesk.com/joinadn
The Building Coder -- http://thebuildingcoder.typepad.com

[Anonymous]

Hey,

Not sure if you solved this but it could be due to a bug in VS2010.

You should check the paths of your dlls in your project file. Open *.csproj and search for the missing assembly or dll. Check the path. If the path is wrong, directly edit the project file and reload the project in vs2010. 

Then build the project.

Kind regards,

Patrick