Different between Debug and Release in VS2017

This forum is meant for questions and discussions about the X# language and tools
Frank Müßner
Posts: 280
Joined: Sat Dec 12, 2015 2:22 pm
Location: Germany

Different between Debug and Release in VS2017

Post by Frank Müßner »

Ok Wolfgang,

Thank you for your Help. I will look what Chris or Robert say.

Frank
Frank Müßner
Posts: 280
Joined: Sat Dec 12, 2015 2:22 pm
Location: Germany

Different between Debug and Release in VS2017

Post by Frank Müßner »

here my Settings:
debug.png
debug.png (59.11 KiB) Viewed 538 times
release.png
release.png (57.91 KiB) Viewed 538 times
Frank
FFF
Posts: 1584
Joined: Fri Sep 25, 2015 4:52 pm
Location: Germany

Different between Debug and Release in VS2017

Post by FFF »

Frank,
what Wolfgang probably meant: attach your new test app here, so that Chris/Robert may try directly...

Karl
Regards
Karl
(on Win8.1/64, Xide32 2.20, X#2.20.0.3)
Frank Müßner
Posts: 280
Joined: Sat Dec 12, 2015 2:22 pm
Location: Germany

Different between Debug and Release in VS2017

Post by Frank Müßner »

Hi Karl,
that is only the VulcanApplikation from X#. That run not in debug or release.
Perhaps someone can confirm this?

Frank
Attachments
VulcanApplication2.zip
(213.98 KiB) Downloaded 50 times
User avatar
wriedmann
Posts: 3765
Joined: Mon Nov 02, 2015 5:07 pm
Location: Italy

Different between Debug and Release in VS2017

Post by wriedmann »

Hi Frank,

I have now tried the sample application in VS 2015 Community, and there it works.

These are the compiler options:
compileroptionsv2015.png
compileroptionsv2015.png (12.18 KiB) Viewed 538 times
and these the build options:
buildoptions2015.png
buildoptions2015.png (27.1 KiB) Viewed 538 times
Wolfgang
Wolfgang Riedmann
Meran, South Tyrol, Italy
wolfgang@riedmann.it
https://www.riedmann.it - https://docs.xsharp.it
Frank Müßner
Posts: 280
Joined: Sat Dec 12, 2015 2:22 pm
Location: Germany

Different between Debug and Release in VS2017

Post by Frank Müßner »

Hi Wolfgang

Exact the same here!

:-( but with errors

And i have new virtual install fresh VS2017 and X#
The same Error.

Frank
User avatar
wriedmann
Posts: 3765
Joined: Mon Nov 02, 2015 5:07 pm
Location: Italy

Different between Debug and Release in VS2017

Post by wriedmann »

Hi Frank,

if I remember correctly, you don't have Vulcan installed, so the Vulcan runtime DLLs are not in the GAC.

The Vulcan runtime needs not only the VulcanRT.DLL and the VulcanRTFuncs.dll, but also the VulcanMacroCompiler.dll.

Try to put this DLL in your bin folder. And if this does not work, try with the eventlog (Eventviewer). Often errors are visible only there.

Wolfgang
Wolfgang Riedmann
Meran, South Tyrol, Italy
wolfgang@riedmann.it
https://www.riedmann.it - https://docs.xsharp.it
Frank Müßner
Posts: 280
Joined: Sat Dec 12, 2015 2:22 pm
Location: Germany

Different between Debug and Release in VS2017

Post by Frank Müßner »

Hi Wolfgang,

yes, ok that solves the behavior from the Sample Vulcan.

Not my App, that work in Debug and not in Release. Eventviewer show when Release Version start:

Name der fehlerhaften Anwendung: AWINKASSE_ORG_NEU!!!!!!!!!!!!!!!.exe, Version: 0.0.0.0, Zeitstempel: 0x598b1826
Name des fehlerhaften Moduls: mscorlib.ni.dll, Version: 4.7.2101.1, Zeitstempel: 0x59326962
Ausnahmecode: 0xc00000fd
Fehleroffset: 0x003a8193
ID des fehlerhaften Prozesses: 0x2c40
Startzeit der fehlerhaften Anwendung: 0x01d31119c6a0c9a6
Pfad der fehlerhaften Anwendung: E:Visual Studio 2017WinQuickReleaseAWINKASSE_ORG_NEU!!!!!!!!!!!!!!!.exe
Pfad des fehlerhaften Moduls: C:WindowsassemblyNativeImages_v4.0.30319_32mscorlibaff328835c74ccf06c928da8cc8caa0amscorlib.ni.dll
Berichtskennung: 3fa053aa-aeef-43bf-9d99-1d3afd0ef9f0
Vollständiger Name des fehlerhaften Pakets:
Anwendungs-ID, die relativ zum fehlerhaften Paket ist:



Fehlerbucket 129528060615, Typ 5
Ereignisname: CLR20r3
Antwort: Nicht verfügbar
CAB-Datei-ID: 129744407356

Problemsignatur:
P1: AWINKASSE_ORG_NEU!!!!!!!!!!!!!!!
P2: missing
P3: 598b1826
P4: mscorlib
P5: 4.7.2101.1
P6: 59326962
P7: 111c
P8: 0
P9: System.StackOverflowException
P10:



Frank
User avatar
wriedmann
Posts: 3765
Joined: Mon Nov 02, 2015 5:07 pm
Location: Italy

Different between Debug and Release in VS2017

Post by wriedmann »

Hi Frank,

in the errormessage is something I don't like:

Code: Select all

Ereignisname: CLR20r3
This seems to call the .NET Framework 3.x and not the 4.x. Try to search in your options if there is something strange with the framework settings.

Wolfgang
Wolfgang Riedmann
Meran, South Tyrol, Italy
wolfgang@riedmann.it
https://www.riedmann.it - https://docs.xsharp.it
User avatar
Chris
Posts: 4936
Joined: Thu Oct 08, 2015 7:48 am
Location: Greece

Different between Debug and Release in VS2017

Post by Chris »

Hi Frank,

I think Wolfgang spotted this well, seems there's some kind of mixup in the project with framework version. Could it be you have added references to the .Net 2 versions of the vulcan dlls? There are 2 sets, one for .Net < 4.0 and one for .Net >= 4.0, you must make sure you use the later ones.

Also what about the target framework version, you can see the selected option in project properties, General page. Is this something like ".NETFramework,Version=v4.5.1"?

In any case, please zip and send me the solution, might be something more that's very difficult to spot from distance. I suspect that also has to do with the other issue you see with loading the solution.

Chris
Chris Pyrgas

XSharp Development Team
chris(at)xsharp.eu
Post Reply