Preview | SOLIDWORKS USER FORUM
Use your SOLIDWORKS ID or 3DEXPERIENCE ID to log in.
MBMike Barber25/01/2008
I have a problem with a custom application written by the
company I work for. I was able to reproduce this problem in one of
the eDrawings sample projects. I can't get the "Save As" dialog to
pop up when I make the function call:
Me.AxEModelViewControl1.Save("", True, "")
To reproduce this problem, do the following things:
1) Open up C:\Program Files\Common Files\eDrawings2007\api\examples\Sample1_eDrawings_Console\EDrawingsConsole
2) Open EDrawingsConsole.vbproj using Visual Studio 2005 vb.net
3) Load a Solidworks drawing
4) Click the "Save As" button
My error was that nothing happens - no dialog box opens. This is the error that I've been getting in our custom code application as well. Perhaps it is because it was written in an older version of .NET, and it needs to be converted? When I converted the project, I accepted all the defaults for the conversion options.
Other info:
I'm running eDrawings 2007 version 4, and vb.net 2005.
Please let me know if you have any ideas, or if upgrading to Solidworks / eDrawings 2008 will fix this behavior. I'm suspicious that it is a vb.net 2003 vs 2005 issue, but I haven't confirmed it.
Regards,
Mike Barber
Me.AxEModelViewControl1.Save("", True, "")
To reproduce this problem, do the following things:
1) Open up C:\Program Files\Common Files\eDrawings2007\api\examples\Sample1_eDrawings_Console\EDrawingsConsole
2) Open EDrawingsConsole.vbproj using Visual Studio 2005 vb.net
3) Load a Solidworks drawing
4) Click the "Save As" button
My error was that nothing happens - no dialog box opens. This is the error that I've been getting in our custom code application as well. Perhaps it is because it was written in an older version of .NET, and it needs to be converted? When I converted the project, I accepted all the defaults for the conversion options.
Other info:
I'm running eDrawings 2007 version 4, and vb.net 2005.
Please let me know if you have any ideas, or if upgrading to Solidworks / eDrawings 2008 will fix this behavior. I'm suspicious that it is a vb.net 2003 vs 2005 issue, but I haven't confirmed it.
Regards,
Mike Barber