Hi Robert,
yes, you have done really a great work stabilizing VO - both the IDE and the applications.
Wolfgang
Debugging in Visual Studio
Debugging in Visual Studio
Wolfgang Riedmann
Meran, South Tyrol, Italy
wolfgang@riedmann.it
https://www.riedmann.it - https://docs.xsharp.it
Meran, South Tyrol, Italy
wolfgang@riedmann.it
https://www.riedmann.it - https://docs.xsharp.it
Debugging in Visual Studio
yes, you have done really a great work stabilizing VO - both the IDE and the applications.
Absolutely. Can't remember the last time I had a corrupt repo, but I export all AEFs from time to time and reimport. This was also vastly improved after VO created empty libs on importing other libs and then overwrote these when the non empty AEF came along.
I personally would not need a repo but only a way to quickly see which 'entity' was last changed combined with a way to open just one method in a separate window. Task Canvas does do the 2nd job but not the first.
Dick
Absolutely. Can't remember the last time I had a corrupt repo, but I export all AEFs from time to time and reimport. This was also vastly improved after VO created empty libs on importing other libs and then overwrote these when the non empty AEF came along.
I personally would not need a repo but only a way to quickly see which 'entity' was last changed combined with a way to open just one method in a separate window. Task Canvas does do the 2nd job but not the first.
Dick
Debugging in Visual Studio
Dick
I personally would not need a repo but only a way to quickly see which 'entity' was last changed combined with a way to open just one method in a separate window. Task Canvas does do the 2nd job but not the first.
We have been thinking of storing meta information about a VS solution in a separate file next to the source. This file (most likely a SQLite database) should contain a list of all projects, source files and entities. The plan was to do this to avoid having to rescan the whole solution when you open it. Only changed files would need to be rescanned.
Therefore we would store datetime stamps of the files in database.
Storing datetime stamps of entities might be possible to. The only "challenge" there is that we can't simply delete all entities for a file when we refresh the contents of a file, but we would have to check to see if the text of an entity has changed. And we will have to delete entities that are no longer there in the source file.
Once we have this information we can also add a repository browser like you have in VO to allow you to navigate to a specific entity.
I will discuss this with Fabrice and we will see what can come up with.
Is this something that others would like to see too ?
Robert
I personally would not need a repo but only a way to quickly see which 'entity' was last changed combined with a way to open just one method in a separate window. Task Canvas does do the 2nd job but not the first.
We have been thinking of storing meta information about a VS solution in a separate file next to the source. This file (most likely a SQLite database) should contain a list of all projects, source files and entities. The plan was to do this to avoid having to rescan the whole solution when you open it. Only changed files would need to be rescanned.
Therefore we would store datetime stamps of the files in database.
Storing datetime stamps of entities might be possible to. The only "challenge" there is that we can't simply delete all entities for a file when we refresh the contents of a file, but we would have to check to see if the text of an entity has changed. And we will have to delete entities that are no longer there in the source file.
Once we have this information we can also add a repository browser like you have in VO to allow you to navigate to a specific entity.
I will discuss this with Fabrice and we will see what can come up with.
Is this something that others would like to see too ?
Robert
XSharp Development Team
The Netherlands
robert@xsharp.eu
The Netherlands
robert@xsharp.eu
Debugging in Visual Studio
Hi Robert,
But personally I would put the runtime and the macrocompiler at a much higher priority.
Wolfgang
Even if I currently work in XIDE: yes, that would definitely a big enhancement for Visual Studio, even for other languages like C#.Once we have this information we can also add a repository browser like you have in VO to allow you to navigate to a specific entity.
Is this something that others would like to see too ?
But personally I would put the runtime and the macrocompiler at a much higher priority.
Wolfgang
Wolfgang Riedmann
Meran, South Tyrol, Italy
wolfgang@riedmann.it
https://www.riedmann.it - https://docs.xsharp.it
Meran, South Tyrol, Italy
wolfgang@riedmann.it
https://www.riedmann.it - https://docs.xsharp.it
Debugging in Visual Studio
Hello Robert,
Storing datetime stamps of entities might be possible to. The only "challenge" there is that we can't simply delete all entities for a file when we refresh the contents of a file, but we would have to check to see if the text of an entity has changed. And we will have to delete entities that are no longer there in the source file.
If that can be achieved it would be fantastic. Even a simple list like
Program file Entity name Data last changed Time last changed
and an option to double click on an entry to open it and get the cursor on it would be very helpful. I can safely say that on a day with regular work on my C# Photo program, with opening the project a few times to continue, it takes me several minutes extra to locate the last few methods I was working on. Usually I browse the whole program, or I search for a date if I entered that in a comment, and of course sometimes I know where the method name began with and then I can search on it much quicker. The longer ago I worked on it, the more difficult it is to find back what I was doing last on a certain program. So such a feature could save a day or more lost time (compared to VO) every year.
Maybe this should be a kind of VS plugin (which you might charge for to non FOX members, like the Text Canvas maker does too)?
Dick
Storing datetime stamps of entities might be possible to. The only "challenge" there is that we can't simply delete all entities for a file when we refresh the contents of a file, but we would have to check to see if the text of an entity has changed. And we will have to delete entities that are no longer there in the source file.
If that can be achieved it would be fantastic. Even a simple list like
Program file Entity name Data last changed Time last changed
and an option to double click on an entry to open it and get the cursor on it would be very helpful. I can safely say that on a day with regular work on my C# Photo program, with opening the project a few times to continue, it takes me several minutes extra to locate the last few methods I was working on. Usually I browse the whole program, or I search for a date if I entered that in a comment, and of course sometimes I know where the method name began with and then I can search on it much quicker. The longer ago I worked on it, the more difficult it is to find back what I was doing last on a certain program. So such a feature could save a day or more lost time (compared to VO) every year.
Maybe this should be a kind of VS plugin (which you might charge for to non FOX members, like the Text Canvas maker does too)?
Dick
-
Phil Hepburn
- Posts: 743
- Joined: Sun Sep 11, 2016 2:16 pm
Debugging in Visual Studio
Hello All,
I am not too sure that turning VS into "Dick's style VO Repository" is a good idea - or indeed a worthwhile task !
I am sure there are features and functionality in the 'Source Control' which is being totally over-looked here.
I can't advice on SC because I use it (regularly - many times a day) but only simply and to record new versions before I possibly screw my developing app. Putting down a back-marker, just in case.
"Wheel re-invention" seems to sound like what is proposed.
PLEASE take care ....
My serious 2 cents worth,
Phil.
I am not too sure that turning VS into "Dick's style VO Repository" is a good idea - or indeed a worthwhile task !
I am sure there are features and functionality in the 'Source Control' which is being totally over-looked here.
I can't advice on SC because I use it (regularly - many times a day) but only simply and to record new versions before I possibly screw my developing app. Putting down a back-marker, just in case.
"Wheel re-invention" seems to sound like what is proposed.
PLEASE take care ....
My serious 2 cents worth,
Phil.
Debugging in Visual Studio
I am sure .... being totally over-looked here.
I can't advice on SC because I use it... only simply
Wow, that sounds like a worthwhile advice! You are sure but you don't know how it works where you are so sure about.
Definitely an advice not worth more than 2 cents, this "Phil style advice".
Dick
I can't advice on SC because I use it... only simply
Wow, that sounds like a worthwhile advice! You are sure but you don't know how it works where you are so sure about.
Definitely an advice not worth more than 2 cents, this "Phil style advice".
Dick
-
NickFriend
- Posts: 248
- Joined: Fri Oct 14, 2016 7:09 am
Debugging in Visual Studio
Actually Dick I think Phil has hit the nail on the head.
What you are talking about with this issue of tracking which entities have been modified is a very primitive form of source control. Rather than wasting time turning the XSharp environment into a repo style system, those who need to track carefully entities in this way should invest some time in learning how to use source control.
This will give you not just the ability to know which entities have been edited and when, but options to do side by side comparisons with modified and original code, etc. (as Chris mentioned earlier).
I think this question of date stamps is a total non-issue, the tools for handling it are already there.
Nick
What you are talking about with this issue of tracking which entities have been modified is a very primitive form of source control. Rather than wasting time turning the XSharp environment into a repo style system, those who need to track carefully entities in this way should invest some time in learning how to use source control.
This will give you not just the ability to know which entities have been edited and when, but options to do side by side comparisons with modified and original code, etc. (as Chris mentioned earlier).
I think this question of date stamps is a total non-issue, the tools for handling it are already there.
Nick
-
Phil Hepburn
- Posts: 743
- Joined: Sun Sep 11, 2016 2:16 pm
Debugging in Visual Studio
Hi Nick,
I have just there now 'dug out' some of the information I seem to have accumulated in the Source Control files, I must have been saving during the development recently of my Third Party report printing I was doing.
This seems to be the wrong thread for it so I will go and move to Pearls - "Source Control in VS".
See you all there.
Regards,
Phil.
I have just there now 'dug out' some of the information I seem to have accumulated in the Source Control files, I must have been saving during the development recently of my Third Party report printing I was doing.
This seems to be the wrong thread for it so I will go and move to Pearls - "Source Control in VS".
See you all there.
Regards,
Phil.
Debugging in Visual Studio
Hello Nick,
Those who need to track carefully entities in this way should invest some time in learning how to use source control.
Which source control are you suing that is able to do that?
I used Tortoise combined with AnkhSVN. I've pretty carefully studied it and did not find capabilities to quickly find the last changed entity. You are using the word 'primitive' concerning the VO repo entity sort capabilities and indeed primitive was the word which comes to mind when but that concerned this source control programs. Like manual committing, regular tiresome repair sessions. Plus it hasn't been maintained for the last 2 years.
So I suspect you use something else? Would you care to tell us which and shortly describe how you can quickly fetch your latest changed entities?
As written before: if there's a working solution I'd love to use that. I haven't seen it on my selection process for source control a few years ago but maybe one of the others have improved lately to offer this option now?
Dick
Those who need to track carefully entities in this way should invest some time in learning how to use source control.
Which source control are you suing that is able to do that?
I used Tortoise combined with AnkhSVN. I've pretty carefully studied it and did not find capabilities to quickly find the last changed entity. You are using the word 'primitive' concerning the VO repo entity sort capabilities and indeed primitive was the word which comes to mind when but that concerned this source control programs. Like manual committing, regular tiresome repair sessions. Plus it hasn't been maintained for the last 2 years.
So I suspect you use something else? Would you care to tell us which and shortly describe how you can quickly fetch your latest changed entities?
As written before: if there's a working solution I'd love to use that. I haven't seen it on my selection process for source control a few years ago but maybe one of the others have improved lately to offer this option now?
Dick