EDIT
Like suggested in the answers, i submitted this behavior to visual studio, and as a solution, i removed those special characters in the files name.
Visual Studio Team Services (was TFS Online) generated a build of the new version of my the solution, no problems in that. But i noticed that some files that i uploaded that have some special characters (ã,ç,õ), were generated with other characters, like "ç" changed to +º+.
We can't upload files with those characters? Or is some configuration that i am missing in the build configurations or elsewhere? Or some files with wrong encoding ? I uploaded .mp4 files and those special characters were changed as well.
Searched for this particular problem and only found problems with file name too long.
Looks like a bug. You probably need to submit it on the UserVoice site:
https://visualstudio.uservoice.com/forums/121579-visual-studio-2015
Related
I am developing a C# project in Visual Studio 2019. I've read that it should produce .csproj.user files automatically, but it is not. How do I force Visual Studio to produce a .csproj.user file? Thank you.
As mentioned by Hans Passant above, this file is created when there exist user-specific settings. Typically it is created by changing any of the Project->Properties->Debug settings to non-default values (i.e. specifying command line arguments or setting an absolute path for the working directory).
However, as I already have pointed out in the other question, I believe you should not commit this file and find out why you have problems without it. Or rather, why VS adds some relevant information to this file instead of the main csproj.
In my case strangely some references that should have been in the SDK project had found their way into the csproj.user file. I don't know why this happened.
Once I put the references back in the SDK project I had no need for the csproj.user after all.
Today, I wanted to create a Setup file for Project in VS Community 2017. When I import file .sln in Advanced Installer 11.1. I receive notification from Advanced Installer.
Latest Version: Not my exertise, but off the top of my head: 1)The first thing you might want to do is to download the latest version of Advanced Installer (15.0.1 at the time of writing), to see if this solves the whole problem.
Language Issue?: If that doesn't solve things (which it just might do), then 2) I suppose this may have to do with the language. It looks like you have a Vietnamese VS project? That Advanced Installer project you show is set to "English" (look at title bar - it says "English US"). Maybe check the view "Translations". It does not look like Vietnamese is one of the supported, built-in languages for Advanced Installer (as of now). Towards the top right, select "All" in the "Show" box and select Vietnamese.
Path Issue?: 3) Perhaps also try to copy the VS project to a path which does not have Vietnamese character in the file and path name? Then try to run the import again.
VS Project Issue?: 4) Perhaps there are weird characters inside the VS Project that cause the problems? I guess there certainly are characters in there that are not normal, Western characters in your case.
Advanced Installer Community: That was just a couple of thoughts off the top of my head - essentially all about language and encoding, there could obviously be further issues. Also reminding you of the Advanced Installer Community Forums. Please try your luck there if you don't get any good answers here.
Some Links:
https://www.advancedinstaller.com/forums
It seems that my Visual Studio Code is ignoring the encoding that I manually set in the User Settings file.
As you can see in the following image, I added the 8th line, and that is the only modification I made. But, In the diff screen, every special character gets modified:
This is the User Setting file that I have:
The windows1252 encoding works perfectly while editing the file, but it seems to get replaced by utf8 (standard VSCode encoding) while comparing both versions.
By the way, I am using the Visual Studio Team Services extension. Has anyone faced this before?
This seemed to be a problem with the extension itself. Right now, I am using the Azure Repos v 1.144.1 and it is working just fine.
I’m a bit confused about the “Character Encoding” in Rational Team Concert, while having trouble with UTF-8 encoded files that are now stored in RTC. (I never had any trouble with these files before.)
The “Character Encoding” shows up in the Eclipse client (at least) here:
File Compare.
Jazz SCM Properties.
The “Character Encoding” is not displayed in the Visual Studio RTC client, at least I could not find it. (Of course, VS has its own ways to display and change encoding of files, but these are independent of RTC.)
I saw several files that are version controlled with MIME Type text/plain which have different “Character Encoding”s for nearly every revision, sometimes changing from UTF-8 to Cp1252 back and forth. Usually, only a few lines in a large file are changed.
It seems to me that automatic merge with the Visual Studio client regularly, but not always, gets confused with encoding and/or byte order marks and changes non 7-bit-ASCII characters. I cannot reproduce this.
I learned several things from a good answer:
Encoding isn’t stored on the server, it is client-only.
scm set property file.encoding sets a user property (and this even can be set to random value such as foo). However:
As far as I can see, file.encoding is completely ignored by Visual Studio, although this doc says:
To change the encoding for files that are checked in from the CLI or Rational Team Concert Client for Microsoft Visual Studio IDE, run scm set property [...] Example: scm set property file.encoding UTF-8 path/to/file.
tl;dr: My question is: Is this “Character Encoding” and/or “file.encoding” of any relevance, and if yes, what is it used for?
Following the FAQ, it is used by an RTC Client (Eclipse or VS) at the checkin phase.
If the encoding specified there differs from the one used in the file you want to check-in, there will be an error:
Basically, there is a text file that Jazz attempted to read when checking in the project contents that it could not because the content does not adhere to the encoding rules. The error message should provide you with the name of file that caused the problem.
Within Eclipse, you have a default encoding for text files.
To see what it is, from the toolbar select Windows > Preferences... > General > Workspace.
If this is not the encoding for most of your text files, you should change it here.
When working within a team you should decide upon a common encoding that you and your team will use. That encoding should also be available on the server (for annotate to work well). You will need to communicate with the rest of your team what the encoding is.
I have installed Visual Studio 2013 with Update 2 and installed Web Essentials.
I had thought this was going to make adding LESS to my views a piece of cake, but am missing something.
The editor is great, and I imagine that it is compiling to css on save...
But I don't know where the generated css is, and I don't have any clue as to how to get it reference in my view.
I've tried a lot of searching, but can't get through the web of links about installing this and the features of that.
Any help at all will be greatly appreciated.
Thanks!
When you add a .less file and save, the Web Essentials will compile and generate the .css and .min.css files. You will see an arrow in your solution explorer, or you can also confirm in your file system that the files are in the same folder.
Haven't used less with vs2013 but I have used sass and my guess would be the same. By default the generated css gets generated in the same directory as the source (as it seemed to me) but you can check via tools>options>web essentials and there should be a set of options for less compile on save, build and directory to name but a few.
If you right click on the solution there should be an option to create a web essentials settings file for the solution - these create and adds a json file of web essentials settings to the solution which means your settings are local to the solution which could be important if you are changing the output directory.