Versions 4.34a - 4.34i are built with VS2015 Community.  Prior Versions are VS2008 which in most cases could be upgraded to VS2012 without too much difficulty.  Id suggest switching to VS2015.

V4.34i targets .NET 4.5.  .NET should be backward compatible so .NET 4.7 should be compatible.

KMotionCNC, KMotion, and the C++ examples don't use .NET

HTH

Regards

TK

 

Is the newest KFlop 4.34i software still compatible with Visual Studio
2012 using the dotnet framework 4.7?

Thanks. The reason I ask is this:

I've attempted to update my current working app from vb.net/vs 2012/dotnet framework 4.5/KMotion 433q

to

vb.net/vs2012/dotnet framework 4.7/KMotion 434i.

As I usually do with an update of the KFlop, I've updated the firmware of the KFlop and included the newest versions of these files with my application:

DSP_KFLOP (everything in the folder)

KMotion.exe

KMotion_dotNet.dll

KMotion_dotNet_interop.dll

KMotionDLL.dll

KMotionServer.exe

GCodeInterpreter.dll

TCC67.exe

emc.var

....placing these into the debug folder of my updated project.

My app starts, then stops when I attempt

Public WithEvents ThisController As New KM_Controller,

failing with the error:

An exception of type 'KMotion_dotNet.DMException' occurred in KMotion_dotNet.dll but was not handled in user code

Looking into the details of the exception reveals:

{"Unable to load DLL 'KMotion_dotNet_Interop.dll': The specified module could not be found. (Exception from HRESULT: 0x8007007E)"}

Could it be a new dependency of the KMotion_dotNet.dll introduced since KMotion v433q?

 

Versions 4.34a - 4.34i are built with VS2015 Community.  Prior Versions are VS2008 which in most cases could be upgraded to VS2012 without too much difficulty.  Id suggest switching to VS2015.

V4.34i targets .NET 4.5.  .NET should be backward compatible so .NET 4.7 should be compatible.

KMotionCNC, KMotion, and the C++ examples don't use .NET

HTH

Regards

TK

On 5/21/2017 7:39 PM, Sam Marrocco sam.marrocco@... [DynoMotion] wrote:

 

Is the newest KFlop 4.34i software still compatible with Visual Studio
2012 using the dotnet framework 4.7?

I don't recall any new dependencies.  Do the Dynomotion .NET Apps run?

Regards

TK

 

Thanks. The reason I ask is this:

I've attempted to update my current working app from vb.net/vs 2012/dotnet framework 4.5/KMotion 433q

to

vb.net/vs2012/dotnet framework 4.7/KMotion 434i.

As I usually do with an update of the KFlop, I've updated the firmware of the KFlop and included the newest versions of these files with my application:

DSP_KFLOP (everything in the folder)

KMotion.exe

KMotion_dotNet.dll

KMotion_dotNet_interop.dll

KMotionDLL.dll

KMotionServer.exe

GCodeInterpreter.dll

TCC67.exe

emc.var

....placing these into the debug folder of my updated project.

My app starts, then stops when I attempt

Public WithEvents ThisController As New KM_Controller,

failing with the error:

An exception of type 'KMotion_dotNet.DMException' occurred in KMotion_dotNet.dll but was not handled in user code

Looking into the details of the exception reveals:

{"Unable to load DLL 'KMotion_dotNet_Interop.dll': The specified module could not be found. (Exception from HRESULT: 0x8007007E)"}

Could it be a new dependency of the KMotion_dotNet.dll introduced since KMotion v433q?

On 5/22/2017 1:24 PM, Tom Kerekes tk@... [DynoMotion] wrote:

 

Versions 4.34a - 4.34i are built with VS2015 Community.  Prior Versions are VS2008 which in most cases could be upgraded to VS2012 without too much difficulty.  Id suggest switching to VS2015.

V4.34i targets .NET 4.5.  .NET should be backward compatible so .NET 4.7 should be compatible.

KMotionCNC, KMotion, and the C++ examples don't use .NET

HTH

Regards

TK

On 5/21/2017 7:39 PM, Sam Marrocco sam.marrocco@... [DynoMotion] wrote:

 

Is the newest KFlop 4.34i software still compatible with Visual Studio
2012 using the dotnet framework 4.7?

 

I don't recall any new dependencies.  Do the Dynomotion .NET Apps run?

Regards

TK

On 5/22/2017 11:52 AM, Sam Marrocco sam.marrocco@... [DynoMotion] wrote:

 

Thanks. The reason I ask is this:

I've attempted to update my current working app from vb.net/vs 2012/dotnet framework 4.5/KMotion 433q

to

vb.net/vs2012/dotnet framework 4.7/KMotion 434i.

As I usually do with an update of the KFlop, I've updated the firmware of the KFlop and included the newest versions of these files with my application:

DSP_KFLOP (everything in the folder)

KMotion.exe

KMotion_dotNet.dll

KMotion_dotNet_interop.dll

KMotionDLL.dll

KMotionServer.exe

GCodeInterpreter.dll

TCC67.exe

emc.var

....placing these into the debug folder of my updated project.

My app starts, then stops when I attempt

Public WithEvents ThisController As New KM_Controller,

failing with the error:

An exception of type 'KMotion_dotNet.DMException' occurred in KMotion_dotNet.dll but was not handled in user code

Looking into the details of the exception reveals:

{"Unable to load DLL 'KMotion_dotNet_Interop.dll': The specified module could not be found. (Exception from HRESULT: 0x8007007E)"}

Could it be a new dependency of the KMotion_dotNet.dll introduced since KMotion v433q?

On 5/22/2017 1:24 PM, Tom Kerekes tk@... [DynoMotion] wrote:

 

Versions 4.34a - 4.34i are built with VS2015 Community.  Prior Versions are VS2008 which in most cases could be upgraded to VS2012 without too much difficulty.  Id suggest switching to VS2015.

V4.34i targets .NET 4.5.  .NET should be backward compatible so .NET 4.7 should be compatible.

KMotionCNC, KMotion, and the C++ examples don't use .NET

HTH

Regards

TK

On 5/21/2017 7:39 PM, Sam Marrocco sam.marrocco@... [DynoMotion] wrote:

 

Is the newest KFlop 4.34i software still compatible with Visual Studio
2012 using the dotnet framework 4.7?

Those are VS2015 Debug libraries.  To run VS2015 debug code you need to have VS2015 installed.

When trying to run your app what version of VS are you using?  Are you trying to run debug code or release code?  Are you re-compiling your code against the newer libraries?

Regards

TK

 

All of the \release apps seems to run fine.
However, none of the \debug versions seem to run.

Debug\KMotionCNC.exe returns dialogs with:
"......can't start because mfc140d.dll is missing from your computer...."
".....can't start because VCRUNTIME140D.dll is missing ....."
".....can't start because ucrtbased.dll is missing......"

as do several other \debug versions of the apps.

JoggerNET.exe fails with "Unable to load DLL 'KMViaVB": The specified module could not be found.

I vaguely recall this being an issue in a distant previous version, something to do with the installations of debugging libraries with certain versions of Visual Studio.....? Does that sound familiar?

On 5/22/2017 3:08 PM, Tom Kerekes tk@... [DynoMotion] wrote:

 

I don't recall any new dependencies.  Do the Dynomotion .NET Apps run?

Regards

TK

On 5/22/2017 11:52 AM, Sam Marrocco sam.marrocco@... [DynoMotion] wrote:

 

Thanks. The reason I ask is this:

I've attempted to update my current working app from vb.net/vs 2012/dotnet framework 4.5/KMotion 433q

to

vb.net/vs2012/dotnet framework 4.7/KMotion 434i.

As I usually do with an update of the KFlop, I've updated the firmware of the KFlop and included the newest versions of these files with my application:

DSP_KFLOP (everything in the folder)

KMotion.exe

KMotion_dotNet.dll

KMotion_dotNet_interop.dll

KMotionDLL.dll

KMotionServer.exe

GCodeInterpreter.dll

TCC67.exe

emc.var

....placing these into the debug folder of my updated project.

My app starts, then stops when I attempt

Public WithEvents ThisController As New KM_Controller,

failing with the error:

An exception of type 'KMotion_dotNet.DMException' occurred in KMotion_dotNet.dll but was not handled in user code

Looking into the details of the exception reveals:

{"Unable to load DLL 'KMotion_dotNet_Interop.dll': The specified module could not be found. (Exception from HRESULT: 0x8007007E)"}

Could it be a new dependency of the KMotion_dotNet.dll introduced since KMotion v433q?

On 5/22/2017 1:24 PM, Tom Kerekes tk@... [DynoMotion] wrote:

 

Versions 4.34a - 4.34i are built with VS2015 Community.  Prior Versions are VS2008 which in most cases could be upgraded to VS2012 without too much difficulty.  Id suggest switching to VS2015.

V4.34i targets .NET 4.5.  .NET should be backward compatible so .NET 4.7 should be compatible.

KMotionCNC, KMotion, and the C++ examples don't use .NET

HTH

Regards

TK

On 5/21/2017 7:39 PM, Sam Marrocco sam.marrocco@... [DynoMotion] wrote:

 

Is the newest KFlop 4.34i software still compatible with Visual Studio
2012 using the dotnet framework 4.7?

I'm using VS2012 and recompiling  my code in debug mode with dotnet framework 4.7 using the KMotion 434i release libraries. I'm guessing that the debug versions of the Kmotion libraries must be requiring the vs2015 debugging libraries, which would suggest that I cannot use the 434i release with vb2012? If so, would this be cured moving to vs2017?

 

Those are VS2015 Debug libraries.  To run VS2015 debug code you need to have VS2015 installed.

When trying to run your app what version of VS are you using?  Are you trying to run debug code or release code?  Are you re-compiling your code against the newer libraries?

Regards

TK

On 5/22/2017 1:56 PM, Sam Marrocco sam.marrocco@... [DynoMotion] wrote:

 

All of the \release apps seems to run fine.
However, none of the \debug versions seem to run.

Debug\KMotionCNC.exe returns dialogs with:
"......can't start because mfc140d.dll is missing from your computer...."
".....can't start because VCRUNTIME140D.dll is missing ....."
".....can't start because ucrtbased.dll is missing......"

as do several other \debug versions of the apps.

JoggerNET.exe fails with "Unable to load DLL 'KMViaVB": The specified module could not be found.

I vaguely recall this being an issue in a distant previous version, something to do with the installations of debugging libraries with certain versions of Visual Studio.....? Does that sound familiar?

On 5/22/2017 3:08 PM, Tom Kerekes tk@... [DynoMotion] wrote:

 

I don't recall any new dependencies.  Do the Dynomotion .NET Apps run?

Regards

TK

On 5/22/2017 11:52 AM, Sam Marrocco sam.marrocco@... [DynoMotion] wrote:

 

Thanks. The reason I ask is this:

I've attempted to update my current working app from vb.net/vs 2012/dotnet framework 4.5/KMotion 433q

to

vb.net/vs2012/dotnet framework 4.7/KMotion 434i.

As I usually do with an update of the KFlop, I've updated the firmware of the KFlop and included the newest versions of these files with my application:

DSP_KFLOP (everything in the folder)

KMotion.exe

KMotion_dotNet.dll

KMotion_dotNet_interop.dll

KMotionDLL.dll

KMotionServer.exe

GCodeInterpreter.dll

TCC67.exe

emc.var

....placing these into the debug folder of my updated project.

My app starts, then stops when I attempt

Public WithEvents ThisController As New KM_Controller,

failing with the error:

An exception of type 'KMotion_dotNet.DMException' occurred in KMotion_dotNet.dll but was not handled in user code

Looking into the details of the exception reveals:

{"Unable to load DLL 'KMotion_dotNet_Interop.dll': The specified module could not be found. (Exception from HRESULT: 0x8007007E)"}

Could it be a new dependency of the KMotion_dotNet.dll introduced since KMotion v433q?

On 5/22/2017 1:24 PM, Tom Kerekes tk@... [DynoMotion] wrote:

 

Versions 4.34a - 4.34i are built with VS2015 Community.  Prior Versions are VS2008 which in most cases could be upgraded to VS2012 without too much difficulty.  Id suggest switching to VS2015.

V4.34i targets .NET 4.5.  .NET should be backward compatible so .NET 4.7 should be compatible.

KMotionCNC, KMotion, and the C++ examples don't use .NET

HTH

Regards

TK

On 5/21/2017 7:39 PM, Sam Marrocco sam.marrocco@... [DynoMotion] wrote:

 

Is the newest KFlop 4.34i software still compatible with Visual Studio
2012 using the dotnet framework 4.7?

I'd recommend trying VS2015 to eliminate that issue.

TK

 

I'm using VS2012 and recompiling  my code in debug mode with dotnet framework 4.7 using the KMotion 434i release libraries. I'm guessing that the debug versions of the Kmotion libraries must be requiring the vs2015 debugging libraries, which would suggest that I cannot use the 434i release with vb2012? If so, would this be cured moving to vs2017?

On 5/22/2017 5:39 PM, Tom Kerekes tk@... [DynoMotion] wrote:

 

Those are VS2015 Debug libraries.  To run VS2015 debug code you need to have VS2015 installed.

When trying to run your app what version of VS are you using?  Are you trying to run debug code or release code?  Are you re-compiling your code against the newer libraries?

Regards

TK

On 5/22/2017 1:56 PM, Sam Marrocco sam.marrocco@... [DynoMotion] wrote:

 

All of the \release apps seems to run fine.
However, none of the \debug versions seem to run.

Debug\KMotionCNC.exe returns dialogs with:
"......can't start because mfc140d.dll is missing from your computer...."
".....can't start because VCRUNTIME140D.dll is missing ....."
".....can't start because ucrtbased.dll is missing......"

as do several other \debug versions of the apps.

JoggerNET.exe fails with "Unable to load DLL 'KMViaVB": The specified module could not be found.

I vaguely recall this being an issue in a distant previous version, something to do with the installations of debugging libraries with certain versions of Visual Studio.....? Does that sound familiar?

On 5/22/2017 3:08 PM, Tom Kerekes tk@... [DynoMotion] wrote:

 

I don't recall any new dependencies.  Do the Dynomotion .NET Apps run?

Regards

TK

On 5/22/2017 11:52 AM, Sam Marrocco sam.marrocco@... [DynoMotion] wrote:

 

Thanks. The reason I ask is this:

I've attempted to update my current working app from vb.net/vs 2012/dotnet framework 4.5/KMotion 433q

to

vb.net/vs2012/dotnet framework 4.7/KMotion 434i.

As I usually do with an update of the KFlop, I've updated the firmware of the KFlop and included the newest versions of these files with my application:

DSP_KFLOP (everything in the folder)

KMotion.exe

KMotion_dotNet.dll

KMotion_dotNet_interop.dll

KMotionDLL.dll

KMotionServer.exe

GCodeInterpreter.dll

TCC67.exe

emc.var

....placing these into the debug folder of my updated project.

My app starts, then stops when I attempt

Public WithEvents ThisController As New KM_Controller,

failing with the error:

An exception of type 'KMotion_dotNet.DMException' occurred in KMotion_dotNet.dll but was not handled in user code

Looking into the details of the exception reveals:

{"Unable to load DLL 'KMotion_dotNet_Interop.dll': The specified module could not be found. (Exception from HRESULT: 0x8007007E)"}

Could it be a new dependency of the KMotion_dotNet.dll introduced since KMotion v433q?

On 5/22/2017 1:24 PM, Tom Kerekes tk@... [DynoMotion] wrote:

 

Versions 4.34a - 4.34i are built with VS2015 Community.  Prior Versions are VS2008 which in most cases could be upgraded to VS2012 without too much difficulty.  Id suggest switching to VS2015.

V4.34i targets .NET 4.5.  .NET should be backward compatible so .NET 4.7 should be compatible.

KMotionCNC, KMotion, and the C++ examples don't use .NET

HTH

Regards

TK

On 5/21/2017 7:39 PM, Sam Marrocco sam.marrocco@... [DynoMotion] wrote:

 

Is the newest KFlop 4.34i software still compatible with Visual Studio
2012 using the dotnet framework 4.7?

 

I'd recommend trying VS2015 to eliminate that issue.

TK

On 5/22/2017 3:09 PM, Sam Marrocco sam.marrocco@... [DynoMotion] wrote:

 

I'm using VS2012 and recompiling  my code in debug mode with dotnet framework 4.7 using the KMotion 434i release libraries. I'm guessing that the debug versions of the Kmotion libraries must be requiring the vs2015 debugging libraries, which would suggest that I cannot use the 434i release with vb2012? If so, would this be cured moving to vs2017?

On 5/22/2017 5:39 PM, Tom Kerekes tk@... [DynoMotion] wrote:

 

Those are VS2015 Debug libraries.  To run VS2015 debug code you need to have VS2015 installed.

When trying to run your app what version of VS are you using?  Are you trying to run debug code or release code?  Are you re-compiling your code against the newer libraries?

Regards

TK

On 5/22/2017 1:56 PM, Sam Marrocco sam.marrocco@... [DynoMotion] wrote:

 

All of the \release apps seems to run fine.
However, none of the \debug versions seem to run.

Debug\KMotionCNC.exe returns dialogs with:
"......can't start because mfc140d.dll is missing from your computer...."
".....can't start because VCRUNTIME140D.dll is missing ....."
".....can't start because ucrtbased.dll is missing......"

as do several other \debug versions of the apps.

JoggerNET.exe fails with "Unable to load DLL 'KMViaVB": The specified module could not be found.

I vaguely recall this being an issue in a distant previous version, something to do with the installations of debugging libraries with certain versions of Visual Studio.....? Does that sound familiar?

On 5/22/2017 3:08 PM, Tom Kerekes tk@... [DynoMotion] wrote:

 

I don't recall any new dependencies.  Do the Dynomotion .NET Apps run?

Regards

TK

On 5/22/2017 11:52 AM, Sam Marrocco sam.marrocco@... [DynoMotion] wrote:

 

Thanks. The reason I ask is this:

I've attempted to update my current working app from vb.net/vs 2012/dotnet framework 4.5/KMotion 433q

to

vb.net/vs2012/dotnet framework 4.7/KMotion 434i.

As I usually do with an update of the KFlop, I've updated the firmware of the KFlop and included the newest versions of these files with my application:

DSP_KFLOP (everything in the folder)

KMotion.exe

KMotion_dotNet.dll

KMotion_dotNet_interop.dll

KMotionDLL.dll

KMotionServer.exe

GCodeInterpreter.dll

TCC67.exe

emc.var

....placing these into the debug folder of my updated project.

My app starts, then stops when I attempt

Public WithEvents ThisController As New KM_Controller,

failing with the error:

An exception of type 'KMotion_dotNet.DMException' occurred in KMotion_dotNet.dll but was not handled in user code

Looking into the details of the exception reveals:

{"Unable to load DLL 'KMotion_dotNet_Interop.dll': The specified module could not be found. (Exception from HRESULT: 0x8007007E)"}

Could it be a new dependency of the KMotion_dotNet.dll introduced since KMotion v433q?

On 5/22/2017 1:24 PM, Tom Kerekes tk@... [DynoMotion] wrote:

 

Versions 4.34a - 4.34i are built with VS2015 Community.  Prior Versions are VS2008 which in most cases could be upgraded to VS2012 without too much difficulty.  Id suggest switching to VS2015.

V4.34i targets .NET 4.5.  .NET should be backward compatible so .NET 4.7 should be compatible.

KMotionCNC, KMotion, and the C++ examples don't use .NET

HTH

Regards

TK

On 5/21/2017 7:39 PM, Sam Marrocco sam.marrocco@... [DynoMotion] wrote:

 

Is the newest KFlop 4.34i software still compatible with Visual Studio
2012 using the dotnet framework 4.7?