William Shakespeare
Earlier this week, after attending Autodesk University 2012, I decided to install Visual Studio Express, so I could go ahead and try my hand at the Autodesk Inventor API.
The download went fine, and soon I was installing away.
As the progress bar cruised along, I noticed one message, "Installing Microsoft .NET Framework 4.5".
I wonder if that's a good idea? I thought. But I dismissed it. I was going to lunch, and my mind was elsewhere. Like food.
When I returned to the office. Visual Studio was merrily installed. All was good in the Kingdom of Laptop.
I wasn't going to be able to work with Visual Studio, so I moved on and worked on other projects.
Eventually, that other project led me to look for some files out of my installation of Autodesk Vault 2013.
![]() |
These are my files, as last left. |
Imagine the camera panning away from me as I scream: "NOOOOOOO!"
![]() |
Now all I see is this! |
I have that sinking feeling. Did the files get deleted? This my personal Vault. Nobody else accesses it. And I didn't delete them.
On a hunch, I change from Detail to Icon view. My files appear! They're still there!
But why won't they show in the Detail View?
Suddenly I remember. .NET Framework 4.5..... The tingle in the back of my neck was trying to tell me something. I remember it's not a good idea to install it with Vault!
All is NOT well in the Kingdom of Laptop.
Fortunately, I had a restore point and was able to "hit the eject button" and return to a state before Visual Studio.
Needless to say, if you're running Autodesk Vault 2013. Stay away from .Microsoft .NET 4.5.
I don't know that .NET 4.5 is bad. As a matter of fact I doubt it. All I know is that it doesn't play well with Autodesk Vault 2013. I wouldn't expect it's going to play well with earlier versions either.
So until Vault supports .NET 4.5, stay safe, stay away.
Don't do what I did!
****EDIT 2-August-2013 ****
I'm a bit late in updating this, I'm afraid it slipped by me. But Service Pack 1 for Autodesk Vault 2013 addes support for .Net 4.5! So if you're seeing this issue, make sure Service Pack 1 is installed.
It a can be downloaded at the link here!
Hey Jonathan, Great post, thanks! Nic
ReplyDelete