However, we cannot set the project dependency due to a limitation in Revit VSTA. We cannot migrate
the RevitViewer sample to VSTA. Therefore, you need to compile RevitViewer as an independent SDK
sample, and then add its DLL as a reference in the Revit VSTA project:
■
When you migrate SDK standard API samples to Revit VSTA, do not copy in any Solution files (*.sln*)
or existing project files (*.csproj or *.vbproj).
■
Toolbar-related samples are unavailable in Revit VSTA.
Revit Macros FAQ
Quick Reference
This section answers frequently asked questions about Revit macros.
Q:
I was expecting to see my newly created macro listed in Macro Manager's categorized list, but it is not
there. Why?
A:
You must successfully build the macro project in the Revit VSTA IDE (use the Build menu) before your
new macros will appear in Macro Manager.
Q:
Do I need to add RevitAPI.dll as a reference when writing a new macro?
A:
No. You do not need to reference Revit DLL files because this step was completed for you. A Revit VSTA
macro project uses Revit.Proxy.dll as a required reference. Revit macros will fail if you delete this reference
in the IDE:
1364 | Chapter 24 Creating Macros with Revit VSTA
Summary of Contents for 24000-000000-9860 - Revit Architecture - PC
Page 1: ...Revit Architecture 2009 User s Guide April 2008 240A1 050000 PM02A ...
Page 4: ......
Page 56: ...18 ...
Page 116: ...78 Chapter 3 Revit Essentials ...
Page 172: ...134 Chapter 4 ProjectViews ...
Page 178: ...Schedule with Grid Lines Schedule with Grid Lines and an Outline 140 Chapter 4 ProjectViews ...
Page 554: ...516 ...
Page 739: ...Curtain wall Curtain Grid Curtain Walls Curtain Grids and Mullions 701 ...
Page 1004: ...966 ...
Page 1136: ...1098 ...
Page 1226: ...1188 ...
Page 1250: ...1212 ...
Page 1276: ...1238 Chapter 20 Design Options ...
Page 1310: ...1272 ...
Page 1366: ...1328 ...
Page 1406: ...1368 ...