Dick,
Have a look at the Thread I started in Pearls, its all about Source Control.
I use one of the built-in versions in VS, there are two.
The one I use seems pretty good as far as I can tell. And since it is from MS should integrate into VS well enough - which it seems to from what I have done.
See you there,
Phil.
Debugging in Visual Studio
Debugging in Visual Studio
Hello Phil,
Thanks for sharing the info. And about my post: please don't feel offended, you are always sharing a great deal of info.
But my whole point is: in VO I can start editing in last or recently changed code of any part of my program in seconds, and that is what I do multiple times a day. Thanks to VO's entity-based repo and it's quick sorting on Last changed. If I were with you or Nick on a Devshare for example challenge you both to be up and running with the code I want in front of me as fast as I do that with VO. You lose, for sure. Whatever else you like more in VS.
In the Pearls, you show me a screen with manually added notes for committed code. Nice, but not what I am looking for. I still don't see any automated and quick way to find & open the recently changed code. If you and Nick tell me it's all in Source Control and that VO is primitive, then show me for VS where & how I can do that faster and better.
If you can't (what I expect because it does not seem to be there) or don't want to (perfectly understandable) I'm fine with your comment that you don't need it because you don't mind spending a few minutes a day more on searching your code. But in that case: don't keep telling it's all in VS and better than in VO because it's simply not true.
Dick
Thanks for sharing the info. And about my post: please don't feel offended, you are always sharing a great deal of info.
But my whole point is: in VO I can start editing in last or recently changed code of any part of my program in seconds, and that is what I do multiple times a day. Thanks to VO's entity-based repo and it's quick sorting on Last changed. If I were with you or Nick on a Devshare for example challenge you both to be up and running with the code I want in front of me as fast as I do that with VO. You lose, for sure. Whatever else you like more in VS.
In the Pearls, you show me a screen with manually added notes for committed code. Nice, but not what I am looking for. I still don't see any automated and quick way to find & open the recently changed code. If you and Nick tell me it's all in Source Control and that VO is primitive, then show me for VS where & how I can do that faster and better.
If you can't (what I expect because it does not seem to be there) or don't want to (perfectly understandable) I'm fine with your comment that you don't need it because you don't mind spending a few minutes a day more on searching your code. But in that case: don't keep telling it's all in VS and better than in VO because it's simply not true.
Dick
Debugging in Visual Studio
Dick
Better than VO? The answer to that is subjective.
But I have managed to get by in my back garden with a spade and wheelbarrow for as long as I can remember. Would I want to move on to a JCB and Dumper truck? Would the effort of learning to drive such things be worthwhile? Only you can make that decision.
So the question becomes is it worth the considerable effort to learn how to use VS? What are the benefits? They depend on you, they depend on the project as it is now, they depend on the project as it may be a few years down the line, plus anything else you can think about.
So the answer is not, and cannot be clear cut.
The ONLY way to learn VS is to use it. This takes time and there is no way round it. And to learn it you must know your project and what you are trying to do to bring it's development to production worthy conclusion.
To help you make the decision I'll say this:
VS is designed to enable development of virtually any type of project you can think of.
.Net projects are basically a set of integrated components (from anywhere)
VS (when you've learnt how to use it) gives facilities to mix and match such components (easily? I think so but again that is subjective)
The value of using VS with a .Net set of components comes about because VS itself uses .Net features: such as intellisense, easily being able to follow a backward chaining route, which together with features like partial classes being able to break larger projects down to manageable sizes and so on.
So all the things you did in VO you will be able to do - and more in VS. And you'll be able to tackle far larger projects.
Terry
Better than VO? The answer to that is subjective.
But I have managed to get by in my back garden with a spade and wheelbarrow for as long as I can remember. Would I want to move on to a JCB and Dumper truck? Would the effort of learning to drive such things be worthwhile? Only you can make that decision.
So the question becomes is it worth the considerable effort to learn how to use VS? What are the benefits? They depend on you, they depend on the project as it is now, they depend on the project as it may be a few years down the line, plus anything else you can think about.
So the answer is not, and cannot be clear cut.
The ONLY way to learn VS is to use it. This takes time and there is no way round it. And to learn it you must know your project and what you are trying to do to bring it's development to production worthy conclusion.
To help you make the decision I'll say this:
VS is designed to enable development of virtually any type of project you can think of.
.Net projects are basically a set of integrated components (from anywhere)
VS (when you've learnt how to use it) gives facilities to mix and match such components (easily? I think so but again that is subjective)
The value of using VS with a .Net set of components comes about because VS itself uses .Net features: such as intellisense, easily being able to follow a backward chaining route, which together with features like partial classes being able to break larger projects down to manageable sizes and so on.
So all the things you did in VO you will be able to do - and more in VS. And you'll be able to tackle far larger projects.
Terry
Debugging in Visual Studio
Hello Terry,
The ONLY way to learn VS is to use it.
Everyone seems to suggest in replies that I don't use VS or don't want to learn it. I use VS for about 8 years now, and the last 3-4 years (too) often. I've read and documented a lot about it. Of course I don't know everything - that even goes for VO, hence my question about debugging and the appreciated reply from Chris how to solve that long open problem.
So all the things you did in VO you will be able to do - and more in VS. And you'll be able to tackle far larger projects.
I haven't seen a project which was too large for VO, so I don't see the advantage of tackling larger projects, but I take your word for it. However, I disagree with your first remark, that is where the whole thread is about the last 2 days. Or can you tell me how I can open the last change entity with 2 clicks?
I bet you can't either and I also bet Robert wouldn't even think about entering it in the X# environment if it was working out of the box. Which I would prefer too of course.
Dick
The ONLY way to learn VS is to use it.
Everyone seems to suggest in replies that I don't use VS or don't want to learn it. I use VS for about 8 years now, and the last 3-4 years (too) often. I've read and documented a lot about it. Of course I don't know everything - that even goes for VO, hence my question about debugging and the appreciated reply from Chris how to solve that long open problem.
So all the things you did in VO you will be able to do - and more in VS. And you'll be able to tackle far larger projects.
I haven't seen a project which was too large for VO, so I don't see the advantage of tackling larger projects, but I take your word for it. However, I disagree with your first remark, that is where the whole thread is about the last 2 days. Or can you tell me how I can open the last change entity with 2 clicks?
I bet you can't either and I also bet Robert wouldn't even think about entering it in the X# environment if it was working out of the box. Which I would prefer too of course.
Dick
Debugging in Visual Studio
Hi Dick
You'd win your bet. I haven't a clue.
But you've really made the point there are things that would be totally inappropriate for the X-Sharp environment. The whole point of XSharp is that it is a subset of the Net environment as a whole.
That is part and parcel of what makes this whole sea of technologies manageable. Manageable by individuals rather than huge teams of people as in the past.
Sorry if my comment caused offence/irritation, but I hope they may have helped some who may be daunted by the scope of VS.
Terry
Terry
You'd win your bet. I haven't a clue.
But you've really made the point there are things that would be totally inappropriate for the X-Sharp environment. The whole point of XSharp is that it is a subset of the Net environment as a whole.
That is part and parcel of what makes this whole sea of technologies manageable. Manageable by individuals rather than huge teams of people as in the past.
Sorry if my comment caused offence/irritation, but I hope they may have helped some who may be daunted by the scope of VS.
Terry
Terry
-
Phil Hepburn
- Posts: 743
- Joined: Sun Sep 11, 2016 2:16 pm
Debugging in Visual Studio
What version of VS are you using ?
Can anyone tell me if the Community (FREE) version of 2015 has Source Control available.
The professional versions of VS certainly do.
Good Luck,
Phil.
Can anyone tell me if the Community (FREE) version of 2015 has Source Control available.
The professional versions of VS certainly do.
Good Luck,
Phil.
Debugging in Visual Studio
Sorry if my comment caused offence/irritation, but I hope they may have helped some who may be daunted by the scope of VS.
Hello Terry,
Don't worry I don't take it personally, but the general tone of the replies seems to be that I don't know a thing about VS and that it is ridiculous to ask for something which I consider a huge time saver because
1 "it's already there" (never followed by proof how and where) or
2 because VS has soooo much more great things (true, but for me the balance is negative) or
3 because the repliers are very satisfied with it (great of course and also remarkable in human behavior how easily people accept objectively provable less efficient/more time consuming code locating methods).
I take it is not possible in VS what I want, and others don't care so it makes little sense for Robert to add it. Fine, I won my bet :cheer: but it's confirmed once more to me why I try to keep using VO as long as possible. I won't bother you all with this anymore.
Dick
Hello Terry,
Don't worry I don't take it personally, but the general tone of the replies seems to be that I don't know a thing about VS and that it is ridiculous to ask for something which I consider a huge time saver because
1 "it's already there" (never followed by proof how and where) or
2 because VS has soooo much more great things (true, but for me the balance is negative) or
3 because the repliers are very satisfied with it (great of course and also remarkable in human behavior how easily people accept objectively provable less efficient/more time consuming code locating methods).
I take it is not possible in VS what I want, and others don't care so it makes little sense for Robert to add it. Fine, I won my bet :cheer: but it's confirmed once more to me why I try to keep using VO as long as possible. I won't bother you all with this anymore.
Dick
Debugging in Visual Studio
Hi Dick,
Actually, it's not that difficult to implement dedicated functionality to find this information, which entities changed last etc. If you keep often backups of your code, you can write a tool that compares your current version of your code with the backups and present in a nice listview or anything which entities were changed last, show a completel graph of changes, all sorts of things.
And it is a lot easier writing tools like that in file based projects that .Net compilers use, than start messing with VO's repo API to read code from it... Maybe there are tool like that already available, if not, you could write them yourself, and make them work exactly as you want them and suit you. That's what I did in XIDE with the export mechanisms that suit me and I can now find the information that _I_ need very easily, easier than in VO.
Chris
Actually, it's not that difficult to implement dedicated functionality to find this information, which entities changed last etc. If you keep often backups of your code, you can write a tool that compares your current version of your code with the backups and present in a nice listview or anything which entities were changed last, show a completel graph of changes, all sorts of things.
And it is a lot easier writing tools like that in file based projects that .Net compilers use, than start messing with VO's repo API to read code from it... Maybe there are tool like that already available, if not, you could write them yourself, and make them work exactly as you want them and suit you. That's what I did in XIDE with the export mechanisms that suit me and I can now find the information that _I_ need very easily, easier than in VO.
Chris
Chris Pyrgas
XSharp Development Team
chris(at)xsharp.eu
XSharp Development Team
chris(at)xsharp.eu
Debugging in Visual Studio
I didn't read the whole thread, sorry if this was posted before.
You want to find the last changed source? google is your friend in finding an extension. Maybe this link? Haven't tried it though.
https://marketplace.visualstudio.com/items?itemName=krizzdewizz.goto-last-edit-location
Thats the beauty of an environment as .NET (or some other heavy used IDE), there are a lot of other guys who have the same problems as us...
Regards,
Otto
You want to find the last changed source? google is your friend in finding an extension. Maybe this link? Haven't tried it though.
https://marketplace.visualstudio.com/items?itemName=krizzdewizz.goto-last-edit-location
Thats the beauty of an environment as .NET (or some other heavy used IDE), there are a lot of other guys who have the same problems as us...
Regards,
Otto
Debugging in Visual Studio
Thanks Otto,but this extension seems to do about the same as Ctrl - Phil described earlier. It works during editing, not when starting a project.
I have already searched VS Marketplace through over 800 results with 'edit' in the search key, without result. I agree with Chris that it probably isn't too difficult to write but even less time consuming is to keep working in VO to get that result
Dick
I have already searched VS Marketplace through over 800 results with 'edit' in the search key, without result. I agree with Chris that it probably isn't too difficult to write but even less time consuming is to keep working in VO to get that result
Dick