It turns out that the message is not quite worded correctly! What it apparently means is that there isn’t enough Virtual Memory available to complete the task, so Revit needs to close. I did a little investigating and contacted Autodesk about the message. And besides, we’re saving to the Network! Everyone says that they have “a ton of space” available, so there’s no way there isn’t enough space on the C. NET 3.5 you still need to put in the 2.Over the past few weeks, I’ve had quite a few people call or email into our support line about getting this message “Not Enough Space on Drive C:” when trying to save their project and Revit then crashing.
Note, v.7 is the version I have installed, but you can check C:\Windows\Microsoft.NET\Framework for what the last few digits of your v2.0 folder is (even if you are developing for.
You should then be able to debug fine in Visual Studio 2010. The workaround is this, edit your file which is located in the same directory as the Revit.exe and add: NET 4.0 debugger even though its a 3.5 or 2.0 application (I don’t believe Revit 2011 supports. Microsoft did some investigation and it seems the problem is Visual Studio 2010 is using the. He was using Revit 2010 and found the debugger did not attach either. I Googled it, and to my surprise, I found a Microsoft Connect support request about this made by a fellow Revit API developer ‘mikecvelide’. I tried manually attaching to the Revit.exe process and that seemed to work, but this is a bit of a pain, why doesn’t it automatically attach? After some investigation, it seemed that Visual Studio was not attaching to the Revit.exe process as it should. My API code threw an error, but it was not caught in the debugger, and none of my breakpoints were not hit. Straight away I came across a stumbling block. I have installed it and have started working on my Revit API tools with it.
Visual Studio 2010 is now officially out, and it is great! Some excellent new features, the new look is great, and you can drag code windows to different monitors!
0 kommentar(er)
