Today at Connect 2016 Microsoft Launched the new version of Visual Studio called Visual Studio 2017
There are many new features in this product. The first and also first visible difference is that the installation process has dramatically changed. You no longer have to download and install many giga bytes of information to run Visual Studio. In stead you now can select a workload and only the elements needed for this particular work will be installed.
Typical workloads are .Net desktop development, Universal Windows Platform development and many more.
Installation will run much smoother after that and the whole footprint of Visual Studio will be much smaller.
We at XSharp are ready for this new version, as we already have indicated in earlier news posts.
We are proud that we are one of the so-called "Sim Ship partners" for Visual Studio 2017, 3rd party vendors whose product is ready for VS 2017 from day 1.
We have created a new installer for our FOX subscribers which will integrate the X# product in Visual Studio 2015 and/or Visual Studio 2017. A public installer is expected around Christmas time.
The new installer will be available for download later this week. Please give us some time to test the latest Visual Studio build, to be sure nothing serious has changed.
To celebrate the release of Visual Studio 2017 we have a special introductionary price for new FOX subscribers: new FOX subscribers will get a 30% discount when they use the Coupon Code VS2017 during the order process.
Click here to subscribe to the the FOX program immediately and to qualify for the 30% discount.
This discount will be available until January 31st 2017.
Good to know of the new promotion of 30% discount. Our peso is now getting battered, lowest value in decades, means our licensing budget will up to 20% to 40%. I wish VO runtime is soon supported without using Vn; and VO apps with bBrowser may wished bBrowser will create a native X# conversion plan.
Just to be completely clear, x# does not require VN to be installed in your machine in order to compile VO-style apps, it is only some of the runtime dlls that are needed and if you have a license for any version of them, it should be enough.
The change to our x# runtime will be transparent, all you'll need to do is replace your references to VulcanRTFuncs.dll to XSharpRTFuncs.dll etc. He have done some work already on the x# runtime, once the compiler is VO-ready we will focus on that.
As for bBrowser and any other tool, it will very soon be possible to simply recompile it in x#, probably with zero code changes or very few at most. And you can also already use their binary form from x# if you like.
Chris
My VO apps uses bBrowser. I do not have any Vulcan app. What I need is X# able to port my app to .NET without any need of Vulcan Runtime. Because I am using bBrowser, do bBrowser for Vulcan will work with X#. Last time I check in bbrowser.de, I do not see any X# version just yet, or maybe I am wrong.
I wish I am wrong.
Thanks,
Rene
In order to use the binaries, there is no need for a x#-specific version, the vulcan version should already work also with x# "as is", by using the vulcan runtime. But since you don't have that, you will need to wait a few more months, until we release the x# runtime.
As for a completely x# specific version, all that Joachim will need to do in order to produce one, is to simply recompile his code with x#. In the same way, you will be able to recompile the VOSDK libraries that you have from VO, so you can use them in x#. Compiler-wise, we are getting very close to that, already 2-3 of the libraries compile with no or minor changes, we're still working on the rest.
Chris
I think I got a good deal with X# (maybe it is the right time to support you guys), so far, I am not in a hurry to move our VO apps to .NET but it should not be later than 2018.
I hope Joachim's reading this, bBrowser is important to my move to X#, but it is not critical. It means, I can replace it with another, hence. it will be a lot of work. But I hope bBrowser for X# comes to fruition, I have lots to do.....
Regards,
Rene
Well, any kind of support is always very welcome! :-)
Regarding bBrowser: Right now, the x# compiler (our development version) is capable of compiling most or all existing code that uses standard .Net libraries like WinForms, WPF etc, with very minor or even no changes at all. Once it's capable of doing that also for code that uses the VOSDK (like bBrowser does), then it will be easy enough for Joachim to recompile his code with x# and produce an x# version.
The new x# Beta 8 (which will be released very shortly to FOX subscribers) is a very big step on this direction (things like standard MDI/SDI now require zero changes), but there are still a few things remaining to be done in order to compile bigger apps/libraries. We're getting there closer and closer, day by day, though.
Regarding 2018, that's waaaay into the future! By then, we should be working on other x# dialects, I don't see completely finishing the VO/Vulcan ones taking us more than some months of 2017.
Chris
[quote name="Rene J. Pajaron"]Thanks Chris for the reply.
I think I got a good deal with X# (maybe it is the right time to support you guys), so far, I am not in a hurry to move our VO apps to .NET but it should not be later than 2018.
I hope Joachim's reading this, bBrowser is important to my move to X#, but it is not critical. It means, I can replace it with another, hence. it will be a lot of work. But I hope bBrowser for X# comes to fruition, I have lots to do.....
Regards,
Rene [/quote]
>> Furthermore, if we buy bBrowser for Vn "today",
>> would it be possible to recompile it to X# in our
>> own when X# runtime is ready?
Absolutely!
Chris
I am moving conversion of our VO apps to X# earlier than I had planned (a full year ahead). Maybe it is time to start saying goodbye to my beloved VO. I have full year for this baby....
Regards,
Rene