cecilchamp wrote: I am not sure where I heard about this product, probably on one of the XSharp forums.:It's called JetBrains Rider. www.jetbrains.com/rider/
Is anyone using this IDE? I would like to know what anyone here thinks about it.
Heard about it, but so far my preferred IDE is XIDE... Have not needed anything more...
George, South Africa
XIDE is my development choice, I use Visual Studio only when absolutely needed.
XIDE is fast and code centric, and works also on small monitors, and is also usable on my tablet PC.
And apart form the fact that is written in X#, the author, Chris Pyrgas, is really helpful and has implemented a lot of our suggestions.
The only problem I have with it: it does not supports XAML - not because Chris has not tried to implement it, but because some functionalities needed by XAML are implemented in Visual Studio and not in the compiler.
One of the problems that you may have with XIDE is that the terminology is different from FoxPro.
What FoxPro calls a Project is called an Application in XIDE.
A project in XIDE is a collection of Applications.
Apart from that and what Wolfgang said about WPF you should be fine with XIDE.
wriedmann wrote: The only problem I have with it: it does not supports XAML - not because Chris has not tried to implement it, but because some functionalities needed by XAML are implemented in Visual Studio and not in the compiler.
To be precise about it, what XIDE does not have is a XAML _visual_ editor, and that's because when I tried to implement it I simply got just too frustrated with how its internals are designed (as an IDE writer I would have to work with its internals, nothing wrong (ok, not much wrong ) with WPF as a system when being used normally from regular apps). But if you simply want to embed an already existing XAML resource to your app, that should be pretty easy actually.
Btw, another limitation of XIDE is that you cannot debug applications compiled in 64bit mode, but only in 32bit mode. It's a limitation of the (external) debugging library I am using unfortunately.
there are two sorts of XAML: compiled XAML and loose XAML.
Loose XAML can be embedded also by XIDE (and that is what I already do for some functionalities of my XIDE written WPF applications), but for WPF forms loose XAML has some limitations.
Normal XAML is compiled to BAML by Visual Studio, and the relative compiler also generates a code file (xx.g.cs for C#, xx.g.prg for X#), and adds this file to the project.
Unfortunately the only way to generate that is to use MSBuild, and it has to be an intermediate step in the compile process because the XAML could reference classes in the application itself.
For me this is not really a problem because I build my windows in code, using my own classes that offer some functionalities, like databinding of the DataGridView columns (the columns are defined in the ViewModel, and not in the View), and also the possibility to immediatly implement different languages into the forms.