-
Posts
-
By +sphbecker · Posted
LP cores are MUCH lower power than Efficiency cores. Efficiency cores never really lived up to their name, but they did add a meaningful amount of performance in multithreaded loads, so Intel isn't going to remove them. -
By WrongHead™ · Posted
I don't usually say this, but WTF Microsoft?! Do you hate your customers, or do you just really not care at all? Windows Hello is one of the useful Windows features, and now you're effing it up. -
By +Sledge · Posted
Spartacore -
By matthiew · Posted
There's a lot of bloat in Windows 11, but battery optimisation is not bloatware. -
By matthiew · Posted
Why on earth are you advising people to turn on a pre-release feature which does not work yet?
-
-
Recent Achievements
-
matthiew went up a rank
Veteran
-
Motoman26 went up a rank
Enthusiast
-
M. Murcek went up a rank
Mentor
-
treker_ed went up a rank
Explorer
-
CHUNWEI went up a rank
Apprentice
-
-
Popular Contributors
-
Tell a friend
Question
Linkinfamous
Hey. I have an xml file that I find myself constantly tweaking. The only problem is that it's stored in utf-16, because, well, that's what the framework defaulted to when it serialzed it. I have no issues with the encoding, except for the fact that it's a small pain for Visual Studio to open it, when I do it so often to so many.
Basically, if I just open the file, I get a bunch of asian characters. If I right click the file and choose to open it with the XML Editor (With Encoding) and pick 'auto-detect' for the encoding, it works. I mapped the XML file format to the XML Editor (With Encoding), but I still get the annoying 'pick your encoding' window. Any way to get rid of it?
Small annoyance really, I can live with it...but I'd rather not.
Link to comment
https://www.neowin.net/forum/topic/439617-visual-studio-2005-xml-editor-problem/Share on other sites
3 answers to this question
Recommended Posts