SolidWorks » Note to Remember

Restore .NET Framework back to its original state

sburke — Sun, 25 Jul 2010 22:42:31 +0000

Background

If you have done a clean re-install of SolidWorks and are still getting strange errors (such as missing dlls, or “unknown file types”), it may well be Microsoft .NET Framework at fault. Most of the time, looking in the Windows Event Viewer will confirm this if there are .NET Framework errors showing up.

The first step is to do a repair of .NET Framework, by going to Add/Remove Programs, right-clicking on .NET Framework (choose 3.5 or 3.1 if present) and going Repair. This should work, however sometimes it doesn’t.

You can also try:
Exploring the SolidWorks DVD and in the prereqs folder run “dotnetfx3.exe” (or dotnetfx3_x64.exe). I tried this however I got strange errors about “mscoree.dll” etc.

Download and usage

If all else fails, you can use a “.NET Framework Cleanup Tool“. It works really well and has worked for me every time. You can download this Executable Tool (in a Zip file) from: http://blogs.msdn.com/b/astebner/archive/2008/08/28/8904493.aspx

Just run the exe file and go “Cleanup Now”.
It takes around 5 minutes to process and at the end you will be prompted to Restart the Computer. Restart the Computer/
After the reboot, look in Add/Remove Programs. If its Windows XP, you will see the original .NET Framework 1.1 listed. Thats perfect.
From the prereqs folder of the SolidWorks DVD run “dotnetfx3.exe” or “dotnetfx3_x64.exe”.
Once this is installed, you should be able to start SolidWorks. (No need to go reinstalling SolidWorks)
Fingers crossed the dll errors or strangeness in SolidWorks will have gone.

Notes:
This worked fine on SolidWorks 2009 and SolidWorks 2010
Search the SolidWorks Knowledge Base for the dll error messages or for errors regarding the feature you are having issues with (such as property tab builder etc.) It will typically tell you if its a .NET issue.
Link to dotnetfx3.exe and dotnetfx3_x64.exe
After running the cleanup tool, rebooting, installing dotnetfx3.exe SolidWorks will work fine.
Installing .NET Framework 3 (the dotnetfx3.exe linked above and on the SW prereqs folder), will install .NET Framework 2.0 and 3.0.
I suggest you run Windows Updates, several times. More than likely a .NET 3.5 will have to be installed. Note also, until you run Windows Updates and install all .NET Frameworks that were in place (in Add/Remove Programs in the very begining), some other installed programs on your computer may give out.
Lastly, use at your own risk!

Cosmetic Threads in Assembly Drawings

sburke — Tue, 22 Jun 2010 23:00:51 +0000

I did come across this before, but forgot about it. Putting it here will remind me not to forget it again.

Query: Cosmetic threads do not appear in Assembly Drawings.

Create a Part with a Hole Wizard Hole with Cosmetic Thread.
Create a Drawing of the Part, the Cosmetic Thread shows up in Plan, Elevation, Section etc.
Create an Assembly with the above Part.
Create a Drawing of the Assembly, Cosmetic Threads do not show by default.

The SolidWorks Knowledge Base provided a quick answer (S-03448). The above functionality is intended. If you want to see cosmetic threads in Assembly Drawings, you have to go Insert -> Model Items -> Cosmetic Thread

Problems inserting Routing Components from the Design Library?

sburke — Fri, 09 Apr 2010 13:52:04 +0000

Working on a piping project recently, I done a pack-and-go to make sure the project would open correctly on another computer. Weeks later when I got back to the project, I worked on the extracted pack-and-go, and started creating a new route, I found I could not insert piping components (flanges, tees etc.) from the Design Library via drag-and-drop. I would see no preview of the part in order to smart mate it into place. When I tried to drag and drop, I got the error “Drag and Drop Failed” and also “This component is already open, would you like to show it..”.

I’ve had this problem before with one or two parts, and what I done was to rename the particular flange in the Design Library to weld neck flange2 and then it would drag and drop in correctly. This time however it was more widespread.

After searching the SolidWorks Knowledge Base on the Customer Portal, I found my problem. My problem was specifically due to the Pack and Go that I done. The pack-and-go copied all my Routing parts from the Design Library into a flat folder. Upon opening this, the routing parts (flanges, elbows etc.) were loaded up from the Project folder rather than the Deisgn Library.

Rule:
Keep all Routing Components (flanges, tees etc.) IN ONE PLACE, i.e. the Design Library
If you open an Assembly with routing components, and SW loads up a flange from Location X, you cannot drag and drop the same flange from Location Y. Use File -> Find References to check where SW loaded files up from.

Note to remember when creating Weldment Profiles

sburke — Thu, 06 Aug 2009 20:24:14 +0000

While reading through some blogs the other evening, I came across this useful essential note to remember when creating weldment profiles.

Before you go “Save As” -> Lib Feat Part (*.sldlfp), you need to PRE-SELECT the sketch. Otherwise when you create the Lib Feat Part, it will be empty (initial sketch gone!).

I came across this note on SolidJot tips for Weldments which was in SW2006, and Yes, this pre-select requirement is still needed in SW2009. I remember this because it happened me a few times, and at the time I thought it was an intermittent issue.

Also just to point out that it is really easy to create weldment profiles, allowing you to easily create structures, frames, patio deckings, railings, chassis’s, etc.. Some people think that if a profile is not in the Ansi Inch or Iso, it can’t be done. Oh yes it can. And SW2009 makes weldments much easier by auto-trimming members, allowing to change the trim-order etc. A nice post including video can be found on rickyjordan.com