This question already has answers here:
What are the differences between Visual Studio Code and Visual Studio?
(14 answers)
Closed 12 days ago.
Apologies if this doesn't belong here. I tried Reddit, but got trolled. I'm just at a loss and am struggling to follow tutorials, etc because of it.
I'm coming from an exclusively Python background and have always used Pycharm. I'm now attempting to learn Java & the React fw and would like to use MS Visual, but am confused on why my interface is completely different from every other one I am seeing.
I realize this is a basic question, but I think if I can just figure it out, I'll be able to resolve a few other issues I'm having as well.
This is what their interface looks like
This is what mine looks like
I've tried researching the issue but have not had any success.
You're using the incorrect software. Your first screenshot is using Visual Studio Code which is a code editor (not an IDE) that is completely separate from the Visual Studio IDE.
Related
For years I have been using VS solo. Now we have added a member to the "team." With this new arrangement, I want to make sure we are not both working on the same code at the same time. Will VS 2022 prevent both of us from opening or making changes to a solution or file if it is open in the other's environment?
This may be a ridiculous question, but as I said, this is a new arrangement for me. I've searched the net for this specific issue and can't find it.
Thanks.
There is a cool GUI solution, like About Visual Studio > Show Details.
But is there any chance I can get the same output from CLI?
Thanks!
Terminal window is not a part of the built-in tools within Visual Studio for Mac. There might be some add-ins or extension for this, but I am not aware.
Here is an VS fro Mac add-in that allows you to open a terminal window and you can do something with CLI.
In addition , Team Foundation Version Control will use GUI Git tool , you can have a look at it .
Thanks, finally I asked the question on relevant MS site and received an answer that there is no such thing.
Meanwhile, I was able to find two similar questions and answers here on SO (which I missed earlier, likely due to different query phrasing, even though I tried many times).
Here they are:
https://stackoverflow.com/a/54393403/2518705
https://stackoverflow.com/a/47096260/2518705
Also note my comments to both of them.
This question already has answers here:
Closed 11 years ago.
Possible Duplicate:
How to compile legacy VB6 code
Where can I find an IDE for VB6? I'm guessing I need to get a copy of Visual Studio 6, but I've been googling for hours and I can't find anything.
I need to do some simple maintenance on an old VB6 application. Upgrading it to .NET would cause lots of work on the deployment and testing side of things so I would prefer to avoid that. And I would rather not resort to notepad and command line compiler either.
Is there any better solution to my problem?
Legal options:
There are many copies of visual studio 6.0 on eBay that look legit.
Find someone that has VB6 and have them fix it.
Get an MSDN subscription (unsure which level is needed - Hans says Universal includes VB6)
If converting to VB.NET is an option, you could check out Microsofts upgrade assement tool at:
http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=9639.
I can't believe VB6 is still alive, not too long ago I had to write an ActiveX control for use with VB6.
Years ago I used to have a visual studio plug in (2003 era) which produced a nice little report showing number of lines per code by solution, then project then class, etc.
I've been looking for something similar ever since with no joy. Can anyone recommend one?
Thanks
it's not exactly what you want but doesn't do Code Metrics the job? And if you want to extract them there are Powertools for it.
PS: I think you need professional or above for this.
This question already has answers here:
Closed 10 years ago.
Possible Duplicate:
No IntelliSense for c++/cli in visual studio 2010?
As the title already states, nothing gets popped up or syntax checked. In the status bar, the following message is displayed.
Intellisense 'Unavailable for C++/CLI'
Usually I am using native C++ in Visual C++ 2010 Express.
In Visual C++ 2008, Intellisense was working correctly for C++/CLI, so I guess it should be working in this version too.
The IntelliSense parser in the C++ IDE was due for an overhaul, it had chronic problems that didn't get better with each release. Random corruption of the .ncb file, the IS database was rampant. For VS2010, it was completely rewritten, a new parser and a new way to store the results. Now an .sdf file, a SQL Compact database. The parser was written by the Edison Design Group, they are famous for being the only ones that ever wrote a C++ parser that completely implements the standard.
Sadly, they didn't have the resources to give C++/CLI the same treatment. The work is deferred, it definitely won't make it for SP1. The connect feedback report is here, only 24 votes. Cast your vote.
EDIT: this was taken care of in VS2012, it again supports IntelliSense for C++/CLI. And C++/CX, a language extension to support WinRT that has a syntax that is very similar to C++/CLI, the likely inspiration to get this work done.
From http://connect.microsoft.com/VisualStudio/feedback/details/459187/intellisense-unavailable-for-c-cli :
Hi,
As the team that invented C++/CLI, we are firm believers that it's one of the best ways to interact with managed code (whether it's to expose native objects or consume managed ones).
I want to make it clear that while we can't address this issue, we reduced support for C++/CLI only due to time and resource constraints. This is NOT an indication that we are distancing ourselves from the technology. You can still see managed classes in Class View, search for symbols, get definitions/declarations and the Winforms designer and Unit Testing functionality continue to work.
Unfortunately, it would have taken a long time to add full support for C++/CLI semantics to our new Intellisense parser and we wanted to get this into the hands of native developers in the meantime. We are sorry we couldn't do it all in one release and we eventually intend to bring this support into the Intellisense engine.
Thanks,
Boris Jabes
Visual C++ Team