fbpx

We have uploaded a new version of the compiler for our FOX subscribers to the Prerelease area on this website. This version fixes several issues that have been reported by our customers.

New features:

VO and Vulcan compatibility:

  • All init procedures are now properly called at program startup. So not only init procedures in the SDK libraries, but also init procedures in 3rd party libraries and in your own code
  • When both a function (static method) and an instance method with the same name can be found, then the compiler will no longer choose the instance method, but will default to the static method, when called inside a class and no SELF: or SUPER: prefix is used.
  • The sizeof operator now returns a DWORD value
  • Added support for EXIT PROCEDURES (PROCEDURE MyProcedure EXIT). These procedures will automatically be called during program shutdown, just before all the global variables in the assembly are cleared.

All dialects

  • We have added support for preprocessor output (ppo) files
  • The code generation for IIF expressions has been improved
  • The code for ACCESS and ASSIGN methods is no longer stored as a separate method, but inlined in the generated Property Get and Property Set.

Bug fixes

This build contains many bug fixes and fixes many smaller and larger incompatibilities with the VO/Vulcan compiler. See the included readme for more information.

 

The technical problems with our news server have been resolved. It is back online now !

We are proud to announce that we have released XSharp Beta 8 to our FOX subscribers,
This version has many new features. The list below shows some of the highlights:

Visual Studio

  • Support for the new Visual Studio 2017
  • We have implemented “Linked Files” in a project. This is useful for example if you have files with common code that you want to include in different projects, like global attributes with company name, product name etc.
  • We have added the ability to “Show all files”.
  • If you add a file with a Form or User Control to your project we will now detect that, and set the subtype of the file. You should see the appropriate icon appear in the project tree
  • Improved Drag and drop in the project explorer
  • The ResX and Settings editor now generate source code. We have also enabled the combo box in these editors that allow you to choose between public and internal classes.

Compiler and Language changes

Some new language features in the Compiler:

  • Object Initializers
  • Collection Initializers
  • When constructing anonymous types, you no longer have to name the fields. If you reference fields or properties from other objects, then the names of these fields/properties will be used for the anonymous type as well

Many improvements in the VO/Vulcan compatibility

  • Default Parameters are now implemented just like in VO and Vulcan.
  • Init Procedures in the main app and the Vulcan SDK Libraries are now called by the main app. We are also initializing the Vulcan macro compiler (calling Init procedure in other libraries will follow shortly)
  • The compiler option Implicit Casts and Conversions (/vo7) has been implemented. You can now also use the @ sign to pass variables by Reference (but we prefer the REF syntax)
  • With these changes you can now successfully compile the standard sdi and mdi examples from VO/Vulcan with X#.

You may have heard about it already, but Microsoft is working very hard to finish the next version of Visual Studio (VsNext or VS 15).

Last week they have released Preview 5. You can read more about this new VS version on https://www.visualstudio.com/en-us/news/releasenotes/vs15-relnotes.

Of course we are working very hard to make sure that X# works with this new version of Visual Studio, and so far this works.

Our latest installer (Beta 7a) detects the installation of VS 15 and integrates into VS15 without problems !

See the picture below for the form designer in action

VS15Preview15

In a couple of weeks, on November 16 & 17 at Connect 2016 more information about this new VS version is expected. Stay tuned, we will keep you informed as well.

 

Unfortunately we are having problems with our news (nntp) server news.xsharp.info.

Hopefully this server will be back and running tomorrow (Novemer 21st).

When that hapens we will let you know.

We have uploaded a new version of the compiler for our FOX subscribers to the Prerelease area on this website. This version fixes several issues that have been reported by our customers.

New features:

  • Anonymous type members no longer have to be named. If you select a property as an anonymous type member then the same property name will be used for the anonymous type as well.
  • Missing closing keywords (such as NEXT, ENDIF, ENDCASE and ENDDO) now produce better error message.
  • We have started work on VO/Vulcan style of skipping arguments in the middle of a list of arguments.
    VO/Vulcan style default parameters of xBase specific datatypes (such as SYMBOL or DATE literals) are not supported yet.
  • IIF Expressions are now also allowed as Expression statement. The generated code will be the same as if an IF statement was used

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.

We have just uploaded new installers for XSharp Beta 7a.
The XPorter tool has also been updated and is included in the installer.
Changes sinces Beta 7:

Compiler

  • The compiler was not accepting wildcard strings for the AssemblyFileVersion Attribute and the AssemblyInformationVersion attribute. This has been fixed
  • The #Pragma commands #Pragma Warnings(Push) and #Pragma Warnings(Pop) were not recognized. This has been fixed.
  • The compiler was not recognizing expressions like global::System.String.Compare(..). This has been fixed

Visual Studio Integration

  • Dependent items in subfolders of a project were not recognized properly and could produce an error when opening a project
  • Fixed a problem in the VulcanApp Template
  • The Windows Forms Editor would not open forms in a file without begin namespace .. end namespace. This has been fixed
  • Source code comments between 'entities' in a source file is now properly saved and restored when the source is regenerated by the form editor
  • Unnecessary blank lines in the generate source code are being suppressed
  • The XPorter tool is now part of the Installation
  • Comments after a line continuation character were not properly colored
  • Changed the XSharp VS Editor Color scheme to make certain items easier to read
  • New managed resource files would not be marked with the proper item type. As a result the resources would not be available at runtime. This has been fixed.

Setup

  • The installer, exe files and documentation are now signed with a certificate