So this is NOT Visual Studio but rather VSCode? Do you have insight into why Microsoft keeps making misleading product names? Would it be so horrible to name it VSCode Online instead of Visual Studio Online?
> Let us know if you have any questions
The website says "Use the programming languages and frameworks of your choice". Will that include building and debugging C++ Win32 MFC applications?
Then later made a new thing called .NET Core which was the same as .NET Framework but more multi platform. Which was confusing so they came up with .NET Standard which was an interface describing compatibility between the other two .NETs
They have their top people working on the .NET jit and compiler, and the VS Code editor. None left for naming conventions.
C ++
++https://visualstudio.microsoft.com/services/visual-studio-on...
Well I just tried it and it's aimed at the feel of VSCode.
>Microsoft keeps making misleading product names
What's with the hostility?
Trying to work in this world, and keep up with what I'm supposed to be using for the platform and application in question. As programmers, we expect some level of complexity, but when Microsoft's lead tech evangelist feels the need to make multiple posts to explain the situation with the product lines, it might have gotten a little out of hand.
I can register my local VSCode just fine. When I connect to a remote ssh connection, and try to register that environment, I get a prompt telling me "Failed to register local environment: Install the Azure Account extension". When I look up that extension, I can install it in the SSH environment, but I get the same error still.
"Presently, running the "Register" command via a full instance of VS Code is the only supported flow, but the scenario you described of hosting a server without a GUI is on the product roadmap."
>Let us know if you have any questions/comments/feedback
1) Shortcut keys. I hit some shortcut during my hello world testing that didn't have the expected effect (because browser). Given how keyboard heavy developing is are there any plans on unifying this more somehow - VS / VSC / VSO?
2) I gather this is still free, but I assume this will be running off azure credits later?
3) The machines seemed a little heavy spec'd for me. Powerful is nice & a big draw card for cloud. But for my personal use case (casual python) I can see the sweet spot being lower.
4) Please fix the permission request wordings on first launch. Very awkwardly phrased & still not entirely sure what it was asking. It was asking for maintaining some mystery permissions when I'm not online or some such thing?
5) Will GPU instances be available?
Thanks
For #3, we’ll be adding a “Basic” SKU soon, that includes 2 cores and 4 GB RAM. Would that be sufficient for your use cases? You can track the progress of this enhancement here: https://github.com/MicrosoftDocs/vsonline/issues/54.
#4: Thanks for the feedback! I’ll look into improving that text this week.
#5: Yep! You can track the progress of this enhancement here: https://github.com/MicrosoftDocs/vsonline/issues/192.
Regarding requirements, you could absolutely run the web editor from a Chromebook! Being able to utilize low-powered devices, while using real-world dev tools, is something we’re excited to enable with this service.
This could be an immediate hit if I could click on a button in Github to open that repo in it with the environment all setup.
I never had anything but problems with my Microsoft and Azure accounts because of confusing UX. If I have to deal with live.microsoft.com I won’t use it. But, if you let me login with GitHub I might try it out. I don’t want to link my GitHub account. I want that to be the primary account used to access VS Live.
I’m guessing that won’t happen though since you’ll want everyone to be ready to use Azure.
[1] In ~/.bashrc: PATH=$PATH:/opt/oryx:/opt/nodejs/lts/bin:/opt/dotnet/sdks/lts
[2] ``` Source directory : /home/vsonline/workspace
Using .NET Core SDK Version: 3.0.100
Restoring packages...
Welcome to .NET Core 3.0! ```
[3] ``` /opt/dotnet/sdks/2.1.802/sdk/2.1.802/Sdks/Microsoft.NET.Sdk/targets/Microsoft.NET.TargetFrameworkInference.targets(137,5): error NETSDK1045: The current .NET SDK does not support targeting .NET Core 3.0. Either target .NET Core 2.1 or lower, or use a version of the .NET SDK that supports .NET Core 3.0 ```
Reusing the name of a past product for a new product that is not entirely related is pretty confusing.
https://www.google.com/search?q=vso
vs code doesn't appear anywhere, however you would have totally owned this:
Is there any guidance on what I would need to do to support VSO? Do I need to do anything?
I'm a bit concerned that it sounds like I have to pay in order to write/test environments. Do you not think this will be a barrier to adoption?
Does the platform support that? Or wants to?
What I would like to stop a comment thread and jump to online-video-session to review some code. Live Share works but requires a stable environment by one of the parties which might be troublesome with some code.
We have a lot more to do in order to make this scenario truly shine, but we’re very excited about the possibilities moving forward. I’d love to hear more about your specific thoughts on PR reviews, and what kind of workflow your team would find compelling.
a) People not currently working on a repo (don't have a local build environment setup) and do tweaks and suggest improvements (e.g. add a unit test to prove make a bug clear) in a async way.
b) A tech lead/senior developer can request the author to join a live session to go explain the whole PR has a bad approach or misses a base guideline on the repo. Not sure on this case how a summary of review session should be added (maybe the PR should have a log of review sessions done).
c) A teach lead takes the PR has an opportunity to ask the whole team to join a review so that he can point out a recurring issues on the repo or to just align ideas on code quality.
Original post read: They linked directly to the GitHub repo in the post with a LICENSE in it.
OK. What you wrote on that web site, "run, and debug your applications from any device", reads like a false advertisement.
I do CAD/CAM/CAE, for that I need a physical GPU. I do embedded, for that I need custom physical hardware, running specific build of Linux. I do multimedia, for that I need a physical GPU with all their hardware codecs. I do GPGPU, same thing.
Maybe you should specify which types of applications are actually supported?
That said, we can definitely make sure to be clearer about where we’re at in our journey towards enabling this promise more broadly. Apologies for the confusion!
In the meantime, we also allow registering your own machines with the service, since we’ll never be able to provide all of the customized environments that devs need. With this “self-hosted environment”, you can benefit from the remote tooling experience (including the web editor), with your own compute. I’d love to hear if this would be helpful for you and your specific workloads.
Hmm, for embedded that would be ARM Linux. Even if you'll support the platform, would be slow.
> I’d love to hear if this would be helpful for you and your specific workloads.
Probably not. I don't like latency, you probably don't have an Azure DC in or near western Balkans.
Even ignoring latency, I don't like clouds in general. Unreliable, often overpriced, aggressive marketing.
Is there a stand-alone that I can host and run in a cloud vm myself?
Let us know if you have any questions/comments/feedback, since we’re very keen to begin working with the broader developer community, and learning how we can continue to improve. Otherwise, check out the service (https://aka.ms/vso), and then let us know what you think (https://GitHub.com/microsoftdocs/vsonline).