Preparing SolidWorks for first use message dialog with add-in

This has little to do with the .NET Framework version.  It has to do with Visual Studio Tools for Applications.  It must configure itself on first use.  you have seen posts on this because VSTA is new for 2010.

I'm not sure why your add-in is requiring this to run.  I'll keep an eye out to see if I come across anything.

I ran across this last week, unfortunately the end result was reformating my computer. I tried reregistering using ngen, uninstalling, resetting my registry, repairing. Eventually I decided it was more effiecient for me to stop messing with it. Id like to know if you do come up with a solution.

Sounds unrelated to what you are describing and likely not directly related to those lines of code.

Try creating a blank add-in that just creates a taskpane in SW so you know it is running, and nothing else, and see if it causes it.

Are you using a stand-alone app that hooks into SW (in which case this isn't an "add-in" by definition). In which case yes VSTA will likely have some form of involvement in the binding process when you cast it to a runtime callable wrapper.

Luke Malpass

AngelSix (SolidWorks Tutorials and Books)

BatchProcess

I too have had the same problem.  I've reloaded Microsoft.NET several times and nothing has worked.  I've contacted my reseller but he only sent the Knowledge Base response, which doesn't give a permanent solution. 

My fix was to write a batch file that I run from my desktop before starting Solidworks.  It takes a few minutes to complete, but once done Solidworks (2012 SP3) starts up immediately.  I've found that I need to do this after each computer shutdown or log off.

I can't believe SW hasn't figured out a permanent solution???  I'm very disappointed.

The batch file is below.

I hope this helps

Best Regards,
John

cd c:\windows

cd microsoft.net

cd framework64

cd v4.0.30319

ngen.exe executequeueditems

Just an FY.......I just had this problem this morning with Version 2012 and the fix that Scott Cleavland gives above worked for me.  Thanks Scott!!

Regards,

Chris

This problem started today, my co-worker did not change anything, SW was working fine for at least a year.  If I logged into my co-worker's machine, SW would start fine.

I had a SW VAR AE instruct me to do the NGEN from (admin) command line repair. In addition to the NGEN command line repair, we also and we went into the Window registry to give him full rights to several SW folders. We checked my co-worker's rights and he had full ADMIN rights. After all of the above repair - no change, still had the problem.

The only thing that did change to his computer, before this happened, is one of those Microsoft updates (20), the updates were not negotiable, they were automatic. I can't see why that would be the root cause, because my computer and (3) other also had the MS update and our SW opened fine with no issues.

I tried the Andries Koorzen solution above, that worked.   I am not sure what else that program does, but at least we can use SW now.

SW2012, SP5, 64bit

Thanks Andries!

Dan Bovinich

If anyone is still unable to get these solutions to work, I have one that may help.

I am still on XP at home and I recently upgraded my installation to 2012 so I can do some work from home. It was getting stuck on the "preparing for first time use" window as others have posted. I had wiped out the previous version of SWX all >NET and Visual Studio items so I could do a complete clean install. Then that happened.

I tried the NGEN fix in above posts but it wouldn't do the trick. In my installation when running the "services.msc" snap in I noticed I only had one item in it. It was the MS .NET Optimization service.

Since it was the only one in there I thought what the heck - might as well give it a go. Sure enough soon as I clicked "Stop Service" the command completed in SWX and now I have use of the program again! Wahoo!! So by way of attempting other known solutions I have found another one!

-Ryno