I am using Visual Studio Team Services. My code contains word in Hebrew.
I build the code with one computer and now I am working on another computer.
When I worked on the first computer every thing was fine.
When I downloaded the code to the second computer the Hebrew word turn to be gibberish. If I look on the code online, he is fine.
what can I do to solve it?
Thanks,
Ditza
Go To Team menu in visual studio and then go to "Connect to team project" option and set the path for tfs and connect thought that.
Related
I wants to use Arduino in vs code Visual Studio Code.
I installed arduino IDE on my local machine on C:\Program Files\Arduino IDE I also added arduino path my Visual Studio Code's setting .json
"arduino.path": "C:\\Program Files\\Arduino IDE",
setting .json
I am using arduino extension.
This is the pic of extension
Any suggestion or recommendations would greatly aid me. I've been struggling to find a solution for this problem for 6 hours.
This was giving me issues for the longest time, too. It seems that the Arduino 2.X IDE doesn't work well with VSCode.
To resolve, use the legacy IDE (Arduino 1.8.X). First, uninstall the 2.X version of Arduino. As of February 2023, you can download the legacy version by going to the Arduino Downloads page and scrolling down to the "Legacy IDE (1.8.X)" section. There's a few different download options. I opted for the one labeled "Windows Win 7 and Newer" since it's a neatly contained executable to install Arduino.
From here, run the executable and install normally. I also reinstalled the Arduino plugin in the Visual Studio marketplace (not sure if necessary, but it doesn't hurt). There's at least three places you could potentially enter the arduino.path:
The one in YOUR PROJECT FILEPATH/.vscode/settings.json
The one in the VS Code User Settings (File>Preferences>Settings> User tab> Search for arduino.path in the search bar)
Same as above, but on the "Workspace" tab instead of "User"
For me, leaving all three empty worked fine. I believe that's because the installer added Arduino to the Windows Path variable. Here's a related post, though, where someone had to configure the path variable in case that doesn't work for you.
Maybe I am just missing something, but I don't get how to setup a blank solution in VSCode (Under Windows or Visual Studio, you are able to just create a new Blank NanoFramework Template, but how can I do that in VSCode :/). I would really like to work with the nanoframework instead of c/c++, but I don't know how to create a blank solution :(.
That option is not currently available.
The main goal of the VS Code extension is to allow (partially) folks on MAC or Linux to work with .NET nanoFramework.
It's not possible to debug on VS Code and you'll only have a full experience on Visual Studio. If you're on Windows, the recommendation is to use Visual Studio.
I am developing Unity game apps on a PC using C#, using Visual Studio Code as the editor. The apps are targeted at PC and Android. Multiplayer uses Photon Pun 2.
The Unity version is 2019.3.14F1 - I don't want to move forward just yet in case of 'unexpected problems'.
The VS Code version was 1.48.3 - and everything was fine, no compile errors, all code working OK etc.
Stupidly, I took Microsoft's advice to update VSC, and VS Code went to 1.50.1. Result of this is that there are all sorts of errors showing up in VS Code relating to the Photon code. All these errors stem back to the 'using Photon.Pun;' line. It says "the type or namespace name 'Pun' does not exist in the namespace 'Photon' (are you missing an assembly reference?)".
The code however does not come up with any compile errors in the Unity editor itself, and it all runs fine, including the Photon parts. The problem is in VS Code.
I realise this is almost certainly as VS Code problem, not Photon, but I am wondering if anyone has met this before and knows how to fix it?
(This is why I do not want to move from 2019.3.14F1 to 2020.whatever at the moment - you never know what might happen).
I had the same problem. Installing different versions of VS Code / VS Community Edition didn't fix anything for me, but this did:
With the project open in VS Code, find all occurrences of
<ReferenceOutputAssembly>false</ReferenceOutputAssembly>
in *.csproj files, and replace them with
<ReferenceOutputAssembly>true</ReferenceOutputAssembly>
Tried rebuilding project files, swapping to a different editor (VS Community Edition 2019 - that was fine), but no difference - VSC persisted with the errors. Rest of intellisense working OK.
In the end, totally uninstalled VSC and reinstalled, and that sorted it out. No idea what the actual fault was.
I was wrong.
To-day, the errors are back.
The reason appears to be that in the process of trying to sort this, I installed VS Community Edition 2019 to see if that worked OK (it did). Then went back to VSC, and - that was fine too. Later I uninstalled VS Community Edition 2019 (it is taking about 4GB). It was uninstalling that which brought the errors back into VSC. Reinstalled VS Community Edition 2019, and it is all fine again.
So, VS Community Edition 2019 installs something that VSC needs - but I haven't yet figured out what it is.
UPDATE:
Gave up. Never managed to find out what VSC wanted and wasn't getting. Instead, reinstalled old version of VSC (1.48.2 from code.visualstudio.com/updates) and it is all fine again.
If still having this problem, all you have to do to fix it is by going to Package manager and install "visual studio editor package"
windows>Package Manager> All Packages /or Unity Registry (depeding on your unity version) search of visual studio editor
if it's already installed delete it and reinstall.
Got it FIXED!
Solution (it was a Unity issue):
In Unity, goto Edit > Preferences > External Tools > External Script Editor, and point it to Visual Studio..
Why this was so hard to find, I have no idea. But now my Photon solutions and namespaces properly transfer from Unity to Visual Studio. Hooah!
Also moved the script to where the photon scripts are
Uninstall the Visual studio community and re-install with latest VSC 2022. It will fix the issue
I'm using Visual Studio Code on Ubuntu. I'm new to Linux/Ubuntu so please excuse me if I'm asking a stupid question.
My question is regarding the Tools menu on Visual Studio under Windows. I don't see a Tools option in VS Code and when I search online I see some references to files/tools but that does not seem to work.
I have tried the option to right click the file in both Explorer in VS Code and the system Explorer but the instructions say to select Open in Command Prompt (or Open in Terminal) but those options don't exist when I right click.
Can someone please advise me and give me a reference if it exists?
Maybe an alternative is to run Microsoft VS using Wine. I have not tried that yet as it seems a little like wishful thinking but I will if someone says it will work.
From the Main Menu, select Help, the 'Welcome' which has Customize Tools and Languages.
I have a Visual Source Safe repository, and some (not all, alas!) of my releases are identified by label. I know how to get by label from the command line, but:
Can I get by label from within Visual Studio?
I'm using Visual Studio 2003 (would the answer be different in other versions of Visual Studio?).
Thanks.
PS. I am hoping to migrate to Team Server soon.
View History on the sourcesafe Project in question, and Include Labels. Highlight the Label you want and click "Get." set options, hit OK, you're done!
edit: pardon me AJ, I was referring to doing a "get" on a label from within the Visual Source Safe interface.
However, assuming you have installed Visual Source Safe on the same machine as Visual Studio, these same functions should be available. Go to Tools -> Options > Source Control and make sure the source control plug-in is set to Microsoft Visual SourceSafe.
With that in place, you should be able to right-click on a Project or Solution in the Solution Explorer, select View History, and follow my previous instructions.