fbpx

Converted VO sample project won't open in Visual Studio 2017

More
10 months 1 week ago #1 by Jelle
Hello,

I tried to follow this tutorial about converting the VO Explorer:

www.xsharp.info/help/example-1-the-vo-explorer-examp.html

I used the exact same Explorer project and the conversion is successful. However when I try to open the solution "Explorer.sln" in Visual Studio 2017, I get the error "Visual Studio cannot open project". I put a screenshot in the attachment.

In your tutorial is no mention of this error, what can I do to fix this so it works the same as the tutorial?

Attachments:

Please Log in or Create an account to join the conversation.

More
10 months 1 week ago #2 by Karl Faller
Hi Jelle,
welcome!
Got curious, tried to follow your proc - but stopped already in Xporter, see screenshots.
You should tell us, which version of X# you use, maybe there's a difference?


HTH
Karl
Attachments:

Please Log in or Create an account to join the conversation.

More
10 months 1 week ago - 10 months 1 week ago #3 by Jelle
Thank you, I am using 1.0.2

I just noticed, if I go inside the explorer folder and then click on "Explorer.xsproj", Visual Studio did load, just like in the tutorial image. Maybe the .sln file is corrupt...
Last edit: 10 months 1 week ago by Jelle.

Please Log in or Create an account to join the conversation.

More
10 months 1 week ago #4 by Wolfgang Riedmann
Replied by Wolfgang Riedmann on topic Converted VO sample project won't open in Visual Studio 2017
Hi Karl,

it seems you have a newer xPorter version than me <g>.

Please try to copy the file xided.dll from your XIDE folder to your xPorter folder. That should solve your problem.

Wolfgang

P.S. I'm in the process of converting VO applications to X# using XIDE, so I'm sure Xporter/VO 1.1.1.0 works.

Please Log in or Create an account to join the conversation.

More
10 months 1 week ago - 10 months 1 week ago #5 by Karl Faller
Jelle,
with Wolfgangs hint, my Xport ran, doubleclicking the sln opened my VS17 Community (albeit slooowly), with no errors, "run" started the example, clicking fileopen it crashed :Prightly, as i had ignored the Xporter's hint to copy my VN-runtime to the target folder...
EDIT: and hadn't added the path to the runtime in Xporters ini-file B)

@Wolfgang: the 1.2.1 i have from Fox d/l...
@Jelle: you should get you the 1.1.1 version from downloads.

HTH
Karl
Last edit: 10 months 1 week ago by Karl Faller. Reason: corrections

Please Log in or Create an account to join the conversation.

More
10 months 1 week ago #6 by Robert van der Hulst
Replied by Robert van der Hulst on topic Converted VO sample project won't open in Visual Studio 2017
Jelle,

I think you have installed VS 2017 AFTER you installed XSharp.
Please run the XSharp setup again and choose to install the Visual Studio integration for Visual Studio 2017.

Robert

XSharp Development Team
The Netherlands
This email address is being protected from spambots. You need JavaScript enabled to view it.

Please Log in or Create an account to join the conversation.

More
10 months 1 week ago - 10 months 1 week ago #7 by Otto Christiaanse
Replied by Otto Christiaanse on topic Converted VO sample project won't open in Visual Studio 2017

Karl Faller wrote: Hi Jelle,
Got curious, tried to follow your proc - but stopped already in Xporter, see screenshots.


There was a bug in the VOXporter installer included with the latest total package. There is fixed version in the download section available.
Last edit: 10 months 1 week ago by Otto Christiaanse.

Please Log in or Create an account to join the conversation.

More
10 months 1 week ago - 10 months 1 week ago #8 by Karl Faller
Otto,
i thought to have the corrected version - which is indeed so, but today i used the link from the startmenu, which still pointed to the old version, thx for the hint! - for the actual problem i did as Wolfgang said, and all was fine...

Edit: digging deeper, i have to say, this is a mess. The faulty exe shows in explorer properties as "Version 1.1.2.0" and shows this in the window caption when started.
The "corrected" one from 20.2. shows in properties 1.0.0.0 (!), the caption shows 1.1.1.0.

@Robert, Chris: my advice is SHORTEN the numbering scheme, and add some "automatics" to keep this info synced, doing by hand is to error prone :dry:

Karl
Last edit: 10 months 1 week ago by Karl Faller. Reason: corrections

Please Log in or Create an account to join the conversation.

More
10 months 1 week ago #9 by Jelle
So I reinstalled VO like you suggested with the latest version, and i now get this error:

How to solve? Did i do something wrong?
Attachments:

Please Log in or Create an account to join the conversation.

More
10 months 1 week ago #10 by Wolfgang Riedmann
Replied by Wolfgang Riedmann on topic Converted VO sample project won't open in Visual Studio 2017
Hi Jelle,

please copy the file XIDED.dll from your XIDE folder to the xPorter/VO folder,
or download the latest xPorter/VO version and install it.

Wolfgang

Please Log in or Create an account to join the conversation.

More
10 months 1 week ago #11 by Jelle
My apologies, I must have read over the fact that 1.1.2.1 is the new version.

This version indeed works! Thank you all, for your help.

Please Log in or Create an account to join the conversation.