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!

Especially useful for macros which loop through lots of operations.

If you have a looping MsgBox() popup, the above CTRL+break doesn’t seem to work. In this case:

Task Manager -> Processes -> swvbaserver.exe (End Process)
Note: SW may have to be restarted to allow a macro to run afterwards.

Reference

Query: Cosmetic threads do not appear in Assembly Drawings.

1. Create a Part with a Hole Wizard Hole with Cosmetic Thread.
2. Create a Drawing of the Part, the Cosmetic Thread shows up in Plan, Elevation, Section etc.
3. Create an Assembly with the above Part.
4. 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

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.

Let me introduce xenocode. I originally came across it for a way to run IE6, IE7 etc for web development purposes.
After a little 2MB app is run, any application can be run within a minute or two. The xenocode website has some examples, from winamp to a DivX player, to Opera, Chrome etc. How about wanting to run Quicktime, without the hassle or large download?!

A few of the main points I found:

• No installation of the program to run.
• Full hardware support.
• Network latency not an issue as application is not streamed when running.
• Initial download of runtime environment does seem to be required.
• Typically used for allowing demo use of software, i.e. IE8 etc.

Whether or not its a good idea, or whether it will take off is a different discussion altogether. It’s just with this, it seems a little more possible.

The install finished fine. No need to restart the PC as I ended Windows Explorer (and left explorer.exe closed for the duration of the install). I started SW2010 up, activated it and that was it. Easy.
I won’t put the Whats New 2010 PDF here. Here are a few things I like:

PhotoView 360:

• Choose a 2d Background Image
• Choose a 3D HDRI Image
• Save a Custom View!

SolidWorks 2010:

• Multi-bodies in Sheet Metal
• SolidWorks RX – Download Graphic Card Drivers automatically
• Mouse Gesture Support
• View Decals in eDrawings and SW w/out PhotoWorks enabled
• SolidWorks Network Monitor (interesting)

That’s it for the moment. Lots and lots more to come.

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

• Multi-Column BOMs
• Toolbars & Hotkeys
• Information about Textures
• Kinematics and animation
• Animating Fluid and Liquid movement

I’ve picked out one of my favourite videos from the 3DVia Channel:

SolidWorks Official Youtube Channel

When I went digging more, I found that SolidWorks has quite an updated Youtube channel with some tutorials (albeit only a few ). Again you will be able to get the RSS feed from http://gdata.youtube.com/feeds/base/users/solidworks/uploads. It’ll be interesting to see what appears there. One tutorial which caught my eye was on creating a chassis for a formula racing kart. The video covered creating a custom weldment profile, creating the 3D sketches, starting with the suspension and finally trimming all the members.

Well I hope to see lots of useful videos getting added to these two channels. On one hand youtube is a good medium for hosting videos, however on the other hand, youtube is blocked in many companies. Hopefully you’ll be able to get an exception or a workaround. The hardest part about the plethora of videos is that there are too many, and a lot of poor quality. Hopefully these will be good ones to watch.

While I was working on an old assembly project, I took some parts, and went “form new subassembly”. It prompted me for a template and off I went opening up the New sub-assembly. I saved regularly. Little did I realise that I was working on a Virtual sub-assembly. After spending 60+minutes working on the sub-assembly, saving it religiously (thinking I had it saved externally). I went back to the main assembly and was fixing a few mate errors when, solidworks froze. I was a little impatient, thinking I had my sub-assembly and 60+ minutes work saved! After re-opening the assembly I saw no sign of my work, and was about to pack it in for the day.

After a bit of looking, I found my virtual assembly and virtual parts
They were located in:
C:\Users\sburke\AppData\Local\Temp
After sorting by Date Modified, the parts were in a folder called “swx5792″. I copied the part out of there and to safety.

Phfew. Thanks SolidWorks. As virtual parts become more and more mainstream, I hope this tip will help somebody and save them some time.