Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.clipper.visual-objects > #11571 > unrolled thread

Very interesting : XSharp development roadmap for 2018

Started bystavros.spanos2@gmail.com
First post2018-05-02 03:30 -0700
Last post2018-05-11 20:37 +0200
Articles 20 on this page of 40 — 5 participants

Back to article view | Back to comp.lang.clipper.visual-objects


Contents

  Very interesting : XSharp development roadmap for 2018 stavros.spanos2@gmail.com - 2018-05-02 03:30 -0700
    Re: Very interesting : XSharp development roadmap for 2018 D.J.W. van Kooten <vankooten@removethis.ic2.com> - 2018-05-09 23:49 +0200
      Re: Very interesting : XSharp development roadmap for 2018 "Wolfgang Riedmann" <wriedmann@gmail.com> - 2018-05-10 07:53 +0200
        Re: Very interesting : XSharp development roadmap for 2018 D.J.W. van Kooten <vankooten@removethis.ic2.com> - 2018-05-11 00:32 +0200
          Re: Very interesting : XSharp development roadmap for 2018 "Wolfgang Riedmann" <wriedmann@gmail.com> - 2018-05-11 12:06 +0200
            Re: Very interesting : XSharp development roadmap for 2018 D.J.W. van Kooten <vankooten@removethis.ic2.com> - 2018-05-11 12:26 +0200
          Re: Very interesting : XSharp development roadmap for 2018 Chris Pyrgas <"chris (at)"@xsharp.eu> - 2018-05-11 16:05 +0300
            Re: Very interesting : XSharp development roadmap for 2018 D.J.W. van Kooten <vankooten@removethis.ic2.com> - 2018-05-11 20:11 +0200
              Re: Very interesting : XSharp development roadmap for 2018 "Wolfgang Riedmann" <wriedmann@gmail.com> - 2018-05-11 20:32 +0200
                Re: Very interesting : XSharp development roadmap for 2018 D.J.W. van Kooten <vankooten@removethis.ic2.com> - 2018-05-12 16:57 +0200
                  Re: Very interesting : XSharp development roadmap for 2018 Chris Pyrgas <"chris (at)"@xsharp.eu> - 2018-05-12 18:52 +0300
                    Re: Very interesting : XSharp development roadmap for 2018 D.J.W. van Kooten <vankooten@removethis.ic2.com> - 2018-05-15 00:06 +0200
                      Re: Very interesting : XSharp development roadmap for 2018 Chris Pyrgas <"chris (at)"@xsharp.eu> - 2018-05-15 01:44 +0300
                        Re: Very interesting : XSharp development roadmap for 2018 D.J.W. van Kooten <vankooten@removethis.ic2.com> - 2018-05-15 12:36 +0200
                  Re: Very interesting : XSharp development roadmap for 2018 "Wolfgang Riedmann" <wriedmann@gmail.com> - 2018-05-13 15:01 +0200
              Re: Very interesting : XSharp development roadmap for 2018 Chris Pyrgas <"chris (at)"@xsharp.eu> - 2018-05-12 16:53 +0300
                Re: Very interesting : XSharp development roadmap for 2018 Karl Faller <mail_withoutthat_@_drei-f_andthat_.de> - 2018-05-13 10:08 +0200
                  Re: Very interesting : XSharp development roadmap for 2018 Chris Pyrgas <"chris (at)"@xsharp.eu> - 2018-05-13 16:01 +0300
                  Re: Very interesting : XSharp development roadmap for 2018 "Wolfgang Riedmann" <wriedmann@gmail.com> - 2018-05-13 15:12 +0200
                Re: Very interesting : XSharp development roadmap for 2018 "Wolfgang Riedmann" <wriedmann@gmail.com> - 2018-05-13 15:13 +0200
                  Re: Very interesting : XSharp development roadmap for 2018 Chris Pyrgas <"chris (at)"@xsharp.eu> - 2018-05-13 16:54 +0300
                    Re: Very interesting : XSharp development roadmap for 2018 Karl Faller <mail_withoutthat_@_drei-f_andthat_.de> - 2018-05-13 17:55 +0200
                      Re: Very interesting : XSharp development roadmap for 2018 Chris Pyrgas <"chris (at)"@xsharp.eu> - 2018-05-13 19:37 +0300
                        Re: Very interesting : XSharp development roadmap for 2018 "Wolfgang Riedmann" <wriedmann@gmail.com> - 2018-05-13 19:03 +0200
                    Re: Very interesting : XSharp development roadmap for 2018 "Wolfgang Riedmann" <wriedmann@gmail.com> - 2018-05-13 18:40 +0200
                      Re: Very interesting : XSharp development roadmap for 2018 Chris Pyrgas <"chris (at)"@xsharp.eu> - 2018-05-14 00:33 +0300
                        Re: Very interesting : XSharp development roadmap for 2018 "Wolfgang Riedmann" <wriedmann@gmail.com> - 2018-05-14 06:08 +0200
                          Re: Very interesting : XSharp development roadmap for 2018 Chris Pyrgas <"chris (at)"@xsharp.eu> - 2018-05-14 15:50 +0300
                            Re: Very interesting : XSharp development roadmap for 2018 "Wolfgang Riedmann" <wriedmann@gmail.com> - 2018-05-14 16:01 +0200
                          Re: Very interesting : XSharp development roadmap for 2018 Karl Faller <mail_withoutthat_@_drei-f_andthat_.de> - 2018-05-14 15:13 +0200
                            Re: Very interesting : XSharp development roadmap for 2018 "Wolfgang Riedmann" <wriedmann@gmail.com> - 2018-05-14 16:03 +0200
                Re: Very interesting : XSharp development roadmap for 2018 D.J.W. van Kooten <vankooten@removethis.ic2.com> - 2018-05-15 00:08 +0200
                  Re: Very interesting : XSharp development roadmap for 2018 Chris Pyrgas <"chris (at)"@xsharp.eu> - 2018-05-15 02:07 +0300
                    Re: Very interesting : XSharp development roadmap for 2018 D.J.W. van Kooten <vankooten@removethis.ic2.com> - 2018-05-15 12:17 +0200
                      Re: Very interesting : XSharp development roadmap for 2018 Karl Faller <mail_withoutthat_@_drei-f_andthat_.de> - 2018-05-15 13:41 +0200
                      Re: Very interesting : XSharp development roadmap for 2018 Chris Pyrgas <"chris (at)"@xsharp.eu> - 2018-05-15 16:13 +0300
                  Re: Very interesting : XSharp development roadmap for 2018 "Wolfgang Riedmann" <wriedmann@gmail.com> - 2018-05-15 05:41 +0200
          Re: Very interesting : XSharp development roadmap for 2018 "Wolfgang Riedmann" <wriedmann@gmail.com> - 2018-05-11 15:57 +0200
            Re: Very interesting : XSharp development roadmap for 2018 D.J.W. van Kooten <vankooten@removethis.ic2.com> - 2018-05-11 19:36 +0200
              Re: Very interesting : XSharp development roadmap for 2018 "Wolfgang Riedmann" <wriedmann@gmail.com> - 2018-05-11 20:37 +0200

Page 2 of 2 — ← Prev page 1 [2]


#11620

FromChris Pyrgas <"chris (at)"@xsharp.eu>
Date2018-05-13 16:54 +0300
Message-ID<pd9fvb$501$1@gioia.aioe.org>
In reply to#11619
Hi Wolfgang,

>> About sharing the same code from XIDE and VS, you just need to create
>> a project/app and add to it the exact same files that the other
>> environment is using.
>
> since you have made the XPorter, you know how to write a VS
> solution/project file, so it should be no problem to maintain one
> synchronized between XIDE and VS...

Yes, exactly the XPorter was the latest tool that we made it editable 
from both XIDE and VS. But it's the same thing for bigger projects, like 
Report Pro etc. That's been the case since the vulcan days, only the VS 
versions of the VOSDK, RP/Classmate etc project files were being 
distributed, but internally I was using VIDE to maintain, edit and 
compile them...

It more or less requires this:
- Create and develop an app with one IDE
- Create a new project with the other IDE.
- Select "Add Existing files" on this IDE and select all the .prg files 
that were created by the other IDE.
- Done :)

OK, in practice you might need to make a few more additional steps, but 
basically that's it as described above...

Chris

[toc] | [prev] | [next] | [standalone]


#11621

FromKarl Faller <mail_withoutthat_@_drei-f_andthat_.de>
Date2018-05-13 17:55 +0200
Message-ID<tlngfdhafrek6va53fe917bkbce55pdtjo@4ax.com>
In reply to#11620
Chris,
i think, Wolfgang meant, to envelop a sln around XIDE's part, so that
one can point  both IDEs to the same "one" file - yeah, that's the VO
spoiled way to handle only one single file <G>.

But i presume, as there are differences in the binaries for tools like
the  form editor, that may be not so the straightforward - albeit it
might be nice ;-)



>Hi Wolfgang,
>
>>> About sharing the same code from XIDE and VS, you just need to create
>>> a project/app and add to it the exact same files that the other
>>> environment is using.
>>
>> since you have made the XPorter, you know how to write a VS
>> solution/project file, so it should be no problem to maintain one
>> synchronized between XIDE and VS...
>
>Yes, exactly the XPorter was the latest tool that we made it editable 
>from both XIDE and VS. But it's the same thing for bigger projects, like 
>Report Pro etc. That's been the case since the vulcan days, only the VS 
>versions of the VOSDK, RP/Classmate etc project files were being 
>distributed, but internally I was using VIDE to maintain, edit and 
>compile them...
>
>It more or less requires this:
>- Create and develop an app with one IDE
>- Create a new project with the other IDE.
>- Select "Add Existing files" on this IDE and select all the .prg files 
>that were created by the other IDE.
>- Done :)
>
>OK, in practice you might need to make a few more additional steps, but 
>basically that's it as described above...
>
>Chris
Regards

Karl

[toc] | [prev] | [next] | [standalone]


#11622

FromChris Pyrgas <"chris (at)"@xsharp.eu>
Date2018-05-13 19:37 +0300
Message-ID<pd9ph7$lms$1@gioia.aioe.org>
In reply to#11621
Hi Karl, Wolfgang,

> i think, Wolfgang meant, to envelop a sln around XIDE's part, so that
> one can point  both IDEs to the same "one" file - yeah, that's the VO
> spoiled way to handle only one single file <G>.
>
> But i presume, as there are differences in the binaries for tools like
> the  form editor, that may be not so the straightforward - albeit it
> might be nice ;-)

Ah, sorry, now I understood! Actually, no, I have very little 
understanding on how the VS project system works :). What I did was to 
just create a simple X# project, take the project files that were auto 
created and use those as templates (you can see them in 
\XSharp\VOXPorter\Templates\) and then the XPorter tools just does a 
text replacements (app name, names of .prg files etc). Didn't worry 
about the rest and this approach has worked fine!

Chris



>
>
>
>> Hi Wolfgang,
>>
>>>> About sharing the same code from XIDE and VS, you just need to create
>>>> a project/app and add to it the exact same files that the other
>>>> environment is using.
>>>
>>> since you have made the XPorter, you know how to write a VS
>>> solution/project file, so it should be no problem to maintain one
>>> synchronized between XIDE and VS...
>>
>> Yes, exactly the XPorter was the latest tool that we made it editable
>>from both XIDE and VS. But it's the same thing for bigger projects, like
>> Report Pro etc. That's been the case since the vulcan days, only the VS
>> versions of the VOSDK, RP/Classmate etc project files were being
>> distributed, but internally I was using VIDE to maintain, edit and
>> compile them...
>>
>> It more or less requires this:
>> - Create and develop an app with one IDE
>> - Create a new project with the other IDE.
>> - Select "Add Existing files" on this IDE and select all the .prg files
>> that were created by the other IDE.
>> - Done :)
>>
>> OK, in practice you might need to make a few more additional steps, but
>> basically that's it as described above...
>>
>> Chris
> Regards
>
> Karl
>

[toc] | [prev] | [next] | [standalone]


#11624

From"Wolfgang Riedmann" <wriedmann@gmail.com>
Date2018-05-13 19:03 +0200
Message-ID<flr9eoFe2kmU1@mid.individual.net>
In reply to#11622
Hi Chris,

would it be possible to implement a callback for a plugin whenever the
project in XIDE is changed in any way? That means when a file is added,
removed, compiler options are changed and so forth... Then a plugin
could implement changes to a VS solution.

Wolfgang

> > i think, Wolfgang meant, to envelop a sln around XIDE's part, so
> > that one can point  both IDEs to the same "one" file - yeah, that's
> > the VO spoiled way to handle only one single file <G>.
> > 
> > But i presume, as there are differences in the binaries for tools
> > like the  form editor, that may be not so the straightforward -
> > albeit it might be nice ;-)
> 
> Ah, sorry, now I understood! Actually, no, I have very little
> understanding on how the VS project system works :). What I did was
> to just create a simple X# project, take the project files that were
> auto created and use those as templates (you can see them in
> \XSharp\VOXPorter\Templates\) and then the XPorter tools just does a
> text replacements (app name, names of .prg files etc). Didn't worry
> about the rest and this approach has worked fine!
> 
> Chris
> 
> 
> 
> > 
> > 
> > 
> > > Hi Wolfgang,
> > > 
> > > > > About sharing the same code from XIDE and VS, you just need
> > > > > to create a project/app and add to it the exact same files
> > > > > that the other environment is using.
> > > > 
> > > > since you have made the XPorter, you know how to write a VS
> > > > solution/project file, so it should be no problem to maintain
> > > > one synchronized between XIDE and VS...
> > > 
> > > Yes, exactly the XPorter was the latest tool that we made it
> > > editable from both XIDE and VS. But it's the same thing for
> > > bigger projects, like Report Pro etc. That's been the case since
> > > the vulcan days, only the VS versions of the VOSDK, RP/Classmate
> > > etc project files were being distributed, but internally I was
> > > using VIDE to maintain, edit and compile them...
> > > 
> > > It more or less requires this:
> > > - Create and develop an app with one IDE
> > > - Create a new project with the other IDE.
> > > - Select "Add Existing files" on this IDE and select all the .prg
> > > files that were created by the other IDE.
> > > - Done :)
> > > 
> > > OK, in practice you might need to make a few more additional
> > > steps, but basically that's it as described above...
> > > 
> > > Chris
> > Regards
> > 
> > Karl
> > 



-- 

[toc] | [prev] | [next] | [standalone]


#11623

From"Wolfgang Riedmann" <wriedmann@gmail.com>
Date2018-05-13 18:40 +0200
Message-ID<flr83jFdp0mU1@mid.individual.net>
In reply to#11620
Hi Chris,

I meant exactly what Karl said: XIDE could generate (and maintain) a
sln and/or VS project file.
So if there is a prg file added to XIDE, it could be added also to the
VS project.

The way around will not work until XIDE starts to use sln files as base
(what will never be the case, I think).

Wolfgang

P.S. I think XIDE will have to learn to use optionally MSBuild,
otherwise XIDE will not be usable for .NET Core projects (AFAIK they
need NUGet). And specially for webservices where no GUI is needed I
would prefer to continue to use XIDE


Chris Pyrgas wrote:

> Hi Wolfgang,
> 
> > > About sharing the same code from XIDE and VS, you just need to
> > > create a project/app and add to it the exact same files that the
> > > other environment is using.
> > 
> > since you have made the XPorter, you know how to write a VS
> > solution/project file, so it should be no problem to maintain one
> > synchronized between XIDE and VS...
> 
> Yes, exactly the XPorter was the latest tool that we made it editable
> from both XIDE and VS. But it's the same thing for bigger projects,
> like Report Pro etc. That's been the case since the vulcan days, only
> the VS versions of the VOSDK, RP/Classmate etc project files were
> being distributed, but internally I was using VIDE to maintain, edit
> and compile them...
> 
> It more or less requires this:
> - Create and develop an app with one IDE
> - Create a new project with the other IDE.
> - Select "Add Existing files" on this IDE and select all the .prg
> files that were created by the other IDE.  - Done :)
> 
> OK, in practice you might need to make a few more additional steps,
> but basically that's it as described above...
> 
> Chris



-- 

[toc] | [prev] | [next] | [standalone]


#11625

FromChris Pyrgas <"chris (at)"@xsharp.eu>
Date2018-05-14 00:33 +0300
Message-ID<pdaasg$1lt8$1@gioia.aioe.org>
In reply to#11623
Hi Wolfgang,

I don't think there's any reason why you should not be able to develop 
.Net Core apps with XIDE, the IDEs really do not do anything 
particularly complicated, they just call the compiler with appropriate 
options and it's the compiler that takes over the rest. I remember it 
was a time during the vulcan days when people were saying that it is 
possible to do compact framework apps absolutely only with VS, while at 
the same time others were already developing CF apps with VIDE and 
vulcan and it actually never ever became possible to develop CF app with 
vulcan and VS!!!

About compiling with MSBuild, yes you are right, XIDE will never support 
it :). At least not itself, you could do a plugin if you want. It's also 
a good idea to add plugin support for project changes notifications for 
creating VS project files, but that's a lot of work for me to add this 
support and then a lot of work for the person who will do the plugin, so 
it's probably easier to add support for at least generating the VS 
project files, all with one go.

I had added some experimental support for that in the past 
(Application|Advanced|Export MSBuild project file) but it is very 
incomplete and totally outdated. It uses classes from 
Microsoft.Build.BuildEngine to do the job, will look into updating and 
improving this functionality.

Chris




> Hi Chris,
>
> I meant exactly what Karl said: XIDE could generate (and maintain) a
> sln and/or VS project file.
> So if there is a prg file added to XIDE, it could be added also to the
> VS project.
>
> The way around will not work until XIDE starts to use sln files as base
> (what will never be the case, I think).
>
> Wolfgang
>
> P.S. I think XIDE will have to learn to use optionally MSBuild,
> otherwise XIDE will not be usable for .NET Core projects (AFAIK they
> need NUGet). And specially for webservices where no GUI is needed I
> would prefer to continue to use XIDE
>
>
> Chris Pyrgas wrote:
>
>> Hi Wolfgang,
>>
>>>> About sharing the same code from XIDE and VS, you just need to
>>>> create a project/app and add to it the exact same files that the
>>>> other environment is using.
>>>
>>> since you have made the XPorter, you know how to write a VS
>>> solution/project file, so it should be no problem to maintain one
>>> synchronized between XIDE and VS...
>>
>> Yes, exactly the XPorter was the latest tool that we made it editable
>> from both XIDE and VS. But it's the same thing for bigger projects,
>> like Report Pro etc. That's been the case since the vulcan days, only
>> the VS versions of the VOSDK, RP/Classmate etc project files were
>> being distributed, but internally I was using VIDE to maintain, edit
>> and compile them...
>>
>> It more or less requires this:
>> - Create and develop an app with one IDE
>> - Create a new project with the other IDE.
>> - Select "Add Existing files" on this IDE and select all the .prg
>> files that were created by the other IDE.  - Done :)
>>
>> OK, in practice you might need to make a few more additional steps,
>> but basically that's it as described above...
>>
>> Chris
>
>
>

[toc] | [prev] | [next] | [standalone]


#11626

From"Wolfgang Riedmann" <wriedmann@gmail.com>
Date2018-05-14 06:08 +0200
Message-ID<flsge9Fm1npU1@mid.individual.net>
In reply to#11625
Hi Chris,

> I don't think there's any reason why you should not be able to
> develop .Net Core apps with XIDE, the IDEs really do not do anything
> particularly complicated, they just call the compiler with
> appropriate options and it's the compiler that takes over the rest. 

I was in the session Fabrice gave about development with .NET Core, and
as far as I was able to understand, .NET Core does not uses
dependencies anymore, but lets MSBuild do all, downloading the needed
libraries with NuGet.
Maybe it is better you ask Fabrice what .NET Core projects need.

.NET Core is the future of .NET development, I think - specially now
that Microsoft has announced to make available WinForms and WPF in .NET
Core 3.0 (but without support for other OS than Windows).

Wolfgang

-- 

[toc] | [prev] | [next] | [standalone]


#11627

FromChris Pyrgas <"chris (at)"@xsharp.eu>
Date2018-05-14 15:50 +0300
Message-ID<pdc0k5$965$1@gioia.aioe.org>
In reply to#11626
Hi Wolfgang,

>> I don't think there's any reason why you should not be able to
>> develop .Net Core apps with XIDE, the IDEs really do not do anything
>> particularly complicated, they just call the compiler with
>> appropriate options and it's the compiler that takes over the rest.
>
> I was in the session Fabrice gave about development with .NET Core, and
> as far as I was able to understand, .NET Core does not uses
> dependencies anymore, but lets MSBuild do all, downloading the needed
> libraries with NuGet.
> Maybe it is better you ask Fabrice what .NET Core projects need.
>
> ..NET Core is the future of .NET development, I think - specially now
> that Microsoft has announced to make available WinForms and WPF in .NET
> Core 3.0 (but without support for other OS than Windows).


It's the same with the normal framework, VS itself does nothing for 
compiling applications, it only calls MSBuild and then it is MSBuild 
that in turns calls the compiler. XIDE just circumvents MSBuild and 
handles the whole process manually, it will be the same with .Net Core.

Chris

[toc] | [prev] | [next] | [standalone]


#11629

From"Wolfgang Riedmann" <wriedmann@gmail.com>
Date2018-05-14 16:01 +0200
Message-ID<fltj5hFticsU1@mid.individual.net>
In reply to#11627
Hi Chris,

ok, I will try that. .NET Core is very important to me as I need it for
the Linux platform (as webservice).

Wolfgang

Chris Pyrgas wrote:

> Hi Wolfgang,
> 
> > > I don't think there's any reason why you should not be able to
> > > develop .Net Core apps with XIDE, the IDEs really do not do
> > > anything particularly complicated, they just call the compiler
> > > with appropriate options and it's the compiler that takes over
> > > the rest.
> > 
> > I was in the session Fabrice gave about development with .NET Core,
> > and as far as I was able to understand, .NET Core does not uses
> > dependencies anymore, but lets MSBuild do all, downloading the
> > needed libraries with NuGet.
> > Maybe it is better you ask Fabrice what .NET Core projects need.
> > 
> > ..NET Core is the future of .NET development, I think - specially
> > now that Microsoft has announced to make available WinForms and WPF
> > in .NET Core 3.0 (but without support for other OS than Windows).
> 
> 
> It's the same with the normal framework, VS itself does nothing for
> compiling applications, it only calls MSBuild and then it is MSBuild
> that in turns calls the compiler. XIDE just circumvents MSBuild and
> handles the whole process manually, it will be the same with .Net
> Core.
> 
> Chris



-- 

[toc] | [prev] | [next] | [standalone]


#11628

FromKarl Faller <mail_withoutthat_@_drei-f_andthat_.de>
Date2018-05-14 15:13 +0200
Message-ID<cq2jfd1voectdmbkmtpndndar8a40a5tgn@4ax.com>
In reply to#11626
Wolfgang,
>that Microsoft has announced to make available WinForms and WPF in .NET
>Core 3.0 (but without support for other OS than Windows).
pmfji, but i thought "cross os" was "the" thing about "core" ?

Regards

Karl

[toc] | [prev] | [next] | [standalone]


#11630

From"Wolfgang Riedmann" <wriedmann@gmail.com>
Date2018-05-14 16:03 +0200
Message-ID<fltjabFtj8iU1@mid.individual.net>
In reply to#11628
Hi Karl,

> > that Microsoft has announced to make available WinForms and WPF in
> > .NET Core 3.0 (but without support for other OS than Windows).

> pmfji, but i thought "cross os" was "the" thing about "core" ?

yes, one of the biggest features. 

But it seems that desktop applications remain more important that
Microsoft had expected, and it seems they are not willing to build a
new GUI for other platforms, so they added WPF and WinForms to .NET
Core.

Wolfgang


-- 

[toc] | [prev] | [next] | [standalone]


#11635

FromD.J.W. van Kooten <vankooten@removethis.ic2.com>
Date2018-05-15 00:08 +0200
Message-ID<sc0kfd1ao9a803aonsavgo82rgiaui5mc5@4ax.com>
In reply to#11612
Replying on message of Sat, 12 May 2018 16:53:22 +0300 from Chris
Pyrgas:


Hello Chris,

>About the "go back/forward" while debugging, no, it's not a VS2017 
>specific feature, this has been available also in XIDE/VIDE for more 
>than 10 years. And in all VS versions of course, at least since VS2005 I 
>think.

Are you sure?

I can find very little about it. I see how it probably should work in
https://www.reddit.com/r/csharp/comments/7iav0w/step_back_while_debugging_in_visual_studio/?st=jh6rshj9&sh=4dfea3a0
but that shows an left pointing arrow which is definitely not present
in my VS 2015 Professional. The other icons I see, this one isn't
there.


>About sharing the same code from XIDE and VS, you just need to create a 
>project/app and add to it the exact same files that the other 
>environment is using. For WPF it is a little more complicated, because 
>of the many "hidden" files VS creates for WPF apps, but it is still very 
>doable, but no need to clutter this ng with that, please send me a WPF 
>project of yours and I will show you exactly how to do it.

Well, that's a great offer which I will make use of in due time - but
I'll first try to figure it out myself.

Do I understand this right:

1 Once setup as a Xide project, I can work on .prg files in the
project from Vide or C# alike. Also when I use the VS WPF editor - the
changed XAML code will compile in Xide?
2 But once I change something (references, adding files like a .prg)
in one environment, I have to add that file manually in the other
environment. Correct?

Thanks, you and Wolfgang, for the samples. I checked them all and in
some cases they will be useful once I decide to really move most of my
VO work to X#. I must say however that chances are pretty high that I
will keep using VO for quite a while for most of my work and use C#/X#
to add only that  functionality is working better in .Net. That
despite all the good (and valid) reasons still much more comfortable.

But maybe a change my mind earlier. Both of you are very convincing
and ok, I know you're right that I should do it - soon ;).

Dick

[toc] | [prev] | [next] | [standalone]


#11637

FromChris Pyrgas <"chris (at)"@xsharp.eu>
Date2018-05-15 02:07 +0300
Message-ID<pdd4oc$c6m$1@gioia.aioe.org>
In reply to#11635
Hi Dick,

>> About the "go back/forward" while debugging, no, it's not a VS2017
>> specific feature, this has been available also in XIDE/VIDE for more
>> than 10 years. And in all VS versions of course, at least since VS2005 I
>> think.
>
> Are you sure?
>
> I can find very little about it. I see how it probably should work in
> https://www.reddit.com/r/csharp/comments/7iav0w/step_back_while_debugging_in_visual_studio/?st=jh6rshj9&sh=4dfea3a0
> but that shows an left pointing arrow which is definitely not present
> in my VS 2015 Professional. The other icons I see, this one isn't
> there.


That's a different think, it's called Historical (some people call it 
hysterical :)) Debugging, it's available since VS 2010 I think. It just 
saves the values of locals etc after each step you make in the debugger, 
so you can view later again what was their value two steps back etc.

What I am talking about is being able to skip a few lines of code, or go 
back to a previous one and execute it again, with updated values in 
locals etc. In VS you can do it while debugging by dragging the small 
yellow arrow in the right part of the editor that points to the line of 
code about to be executed and dropping it to another line in the same 
entity of course. In XIDE you can use it from Debug|Set Next Statement.


> Do I understand this right:
>
> 1 Once setup as a Xide project, I can work on .prg files in the
> project from Vide or C# alike. Also when I use the VS WPF editor - the
> changed XAML code will compile in Xide?

When you compile a WPF project in VS, then the .xaml files are being 
compiled into a binary format (BAML), inside resource files (files with 
.resources extension). In XIDE you would need to add directly those 
files, which will be automatically updated every time you change your 
XAML from VS and build again.

About .prg files, yes you can share them between any IDE you like. You 
can also open and edit them also with notepad if you want, it does not 
make a difference, that's the main advantage of file based compilers, 
compared to the repo system.


> 2 But once I change something (references, adding files like a .prg)
> in one environment, I have to add that file manually in the other
> environment. Correct?

Yes, exactly!


> Thanks, you and Wolfgang, for the samples. I checked them all and in
> some cases they will be useful once I decide to really move most of my
> VO work to X#. I must say however that chances are pretty high that I
> will keep using VO for quite a while for most of my work and use C#/X#
> to add only that  functionality is working better in .Net. That
> despite all the good (and valid) reasons still much more comfortable.

That's fine, it's fair that if you do not really need to move to X#, 
there's no point going to it, just for the sake of being modern or 
anything like that. But first you need to make sure you know well what 
you are missing, in order to make a better decision :)

Chris




>
> But maybe a change my mind earlier. Both of you are very convincing
> and ok, I know you're right that I should do it - soon ;).
>
> Dick
>

[toc] | [prev] | [next] | [standalone]


#11642

FromD.J.W. van Kooten <vankooten@removethis.ic2.com>
Date2018-05-15 12:17 +0200
Message-ID<vjclfd9dn95fdunt35hq9cn7u8fdi2cd7f@4ax.com>
In reply to#11637
Replying on message of Tue, 15 May 2018 02:07:24 +0300 from Chris
Pyrgas:


 Hello Chris,

>In VS you can do it while debugging by dragging the small 
>yellow arrow in the right part of the editor that points to the line of 
>code about to be executed and dropping it to another line in the same 
>entity of course. In XIDE you can use it from Debug|Set Next Statement.

Indeed it does! I never knew that and I couldn't really find something
about it by searching either. Thanks.

>When you compile a WPF project in VS, then the .xaml files are being 
>compiled into a binary format (BAML), inside resource files (files with 
>.resources extension). In XIDE you would need to add directly those 
>files, which will be automatically updated every time you change your 
>XAML from VS and build again.


But does this mean that I have to (re)import a bunch of files every
time I change something in my WPF screen?

>That's fine, it's fair that if you do not really need to move to X#, 
>there's no point going to it, just for the sake of being modern or 
>anything like that. But first you need to make sure you know well what 
>you are missing, in order to make a better decision :)


Yes and you are doing a great job in that.
Dick

[toc] | [prev] | [next] | [standalone]


#11647

FromKarl Faller <mail_withoutthat_@_drei-f_andthat_.de>
Date2018-05-15 13:41 +0200
Message-ID<gohlfd5jc08ompm0k7a3vdtu8l42128cps@4ax.com>
In reply to#11642
On Tue, 15 May 2018 12:17:51 +0200, D.J.W. van Kooten wrote:

>But does this mean that I have to (re)import a bunch of files every
>time I change something in my WPF screen?
AFAIK, if you "add existing" Xide asks, if it should copy the existing
file to "its" folder struc. If you say, "no", Xide should use the
original file, so you shouldn't have to manually sync anything.

Hopefully Chris corrects me, if the above is BS <g>

Regards

Karl

[toc] | [prev] | [next] | [standalone]


#11651

FromChris Pyrgas <"chris (at)"@xsharp.eu>
Date2018-05-15 16:13 +0300
Message-ID<pdemb0$tc2$1@gioia.aioe.org>
In reply to#11642
Hi Dick,

>> In VS you can do it while debugging by dragging the small
>> yellow arrow in the right part of the editor that points to the line of
>> code about to be executed and dropping it to another line in the same
>> entity of course. In XIDE you can use it from Debug|Set Next Statement.
>
> Indeed it does! I never knew that and I couldn't really find something
> about it by searching either. Thanks.


You're welcome!


>> When you compile a WPF project in VS, then the .xaml files are being
>> compiled into a binary format (BAML), inside resource files (files with
>> .resources extension). In XIDE you would need to add directly those
>> files, which will be automatically updated every time you change your
>> XAML from VS and build again.
>
> But does this mean that I have to (re)import a bunch of files every
> time I change something in my WPF screen?

As Karl said, XIDE will be using the exact same physical file on disk, 
which will just have been updated by VS, so no need from you to do 
anything. You would need to re attach it only if you changed the name of 
the form, or you create a new one etc.


>> That's fine, it's fair that if you do not really need to move to X#,
>> there's no point going to it, just for the sake of being modern or
>> anything like that. But first you need to make sure you know well what
>> you are missing, in order to make a better decision :)
>
> Yes and you are doing a great job in that.

:-)

regards,
Chris

[toc] | [prev] | [next] | [standalone]


#11639

From"Wolfgang Riedmann" <wriedmann@gmail.com>
Date2018-05-15 05:41 +0200
Message-ID<flv373F941lU1@mid.individual.net>
In reply to#11635
Hi Dick,

> But maybe a change my mind earlier. Both of you are very convincing
> and ok, I know you're right that I should do it - soon ;).

thanks!

But we can only be convincing because we are very convinced ourselves.

I have a long way to go until all (or my most important) VO
applications are ported. The last announcement about .NET Core 3.0
where even WinForms will be available gives me the certainity that my
applications will have a long life when ported to X# and the WinForms
based library.

Wolfgang


-- 

[toc] | [prev] | [next] | [standalone]


#11606

From"Wolfgang Riedmann" <wriedmann@gmail.com>
Date2018-05-11 15:57 +0200
Message-ID<flllq8F6kdaU1@mid.individual.net>
In reply to#11596
Hi Dick,

reading your message again I have come across another thing:

> But still the number of VO users -still- seem higher to me than 
> those who actively use Vulcan or X#. I would like to learn why 
> by asking comments from VO users.

This seems to be another problem. I know there are a LOT of VO users
out there that are not in contact by anyone of the community.

Let me explain: back in the GrafX days I've done some reselling of VO
for Italian users that don't liked to buy with credit card and
preferred a local reseller. Over the years I have selled a few
licenses, and most of them were names I never heard or read before or
after.

Now, when organizing the Italian meeting with Robert, I've contacted
the people that had buyed a VO or Vulcan license the last 5 years.
No mail bounced, so I assume all the email addresses are still valid.
About 30% answered that they had no time to come, and from the others:
silence.
Alessandro did the same with addresses he had from previous Italian
meetings - and had nearly no answer too.

From some messages that are showing up in the forums from time to time
it seems there are many people working with old VO versions like 2.5 or
even 2.0, and they don't seem to know nothing about newer VO versions
or the Vulcan project or the X# project, or are simply not interested
in any movement.

This may sound a bit negative, but I think it is very near to the
reality, unfortunately.

Wolfgang


-- 

[toc] | [prev] | [next] | [standalone]


#11607

FromD.J.W. van Kooten <vankooten@removethis.ic2.com>
Date2018-05-11 19:36 +0200
Message-ID<orkbfdh4bohv2g2ivgfus69q8guj5bldkf@4ax.com>
In reply to#11606
Replying on message of Fri, 11 May 2018 15:57:26 +0200 from Wolfgang
Riedmann:


 Hello Wolfgang,

>From some messages that are showing up in the forums from time to time
>it seems there are many people working with old VO versions like 2.5 or
>even 2.0, and they don't seem to know nothing about newer VO versions
>or the Vulcan project or the X# project, or are simply not interested
>in any movement.
>
I guess that is indeed the point - quite some VO users use an old
version or even compain that it not free...

Which surprises me because they CAN use X# for free. Why keep using
VO, one would say? And my guess is that most of them can do everything
they need to do in VO comfortably and see little reason to switch
despite the long list Chris gave.

Dick

[toc] | [prev] | [next] | [standalone]


#11610

From"Wolfgang Riedmann" <wriedmann@gmail.com>
Date2018-05-11 20:37 +0200
Message-ID<flm674Fa9eeU1@mid.individual.net>
In reply to#11607
Hi Dick,

> > From some messages that are showing up in the forums from time to
> > time it seems there are many people working with old VO versions
> > like 2.5 or even 2.0, and they don't seem to know nothing about
> > newer VO versions or the Vulcan project or the X# project, or are
> > simply not interested in any movement.
> > 
> I guess that is indeed the point - quite some VO users use an old
> version or even compain that it not free...
> 
> Which surprises me because they CAN use X# for free. Why keep using
> VO, one would say? And my guess is that most of them can do everything
> they need to do in VO comfortably and see little reason to switch
> despite the long list Chris gave.

every change implies work and learning new things, and I think that may
be the most important barrier. And maybe the possibility to break a
working software.

Wolfgang

-- 

[toc] | [prev] | [standalone]


Page 2 of 2 — ← Prev page 1 [2]

Back to top | Article view | comp.lang.clipper.visual-objects


csiph-web