The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
Fair enough, and I didn't mean you specifically. But my point is that if you aren't using some kind of source control you can invite trouble just by glancing at something sideways. Hard drive failure, solar flares, bad hair day, anything you don't prepare for can disrupt your code. That's life.
So I wouldn't blame the technique for the issue. I use the technique in by Build Pack, which is kind of my latest meta project. It works great. And it's easy to build. And build again.
There is a locking issue due to a circular dependency in the build step so you have to build twice the first time, but whatever.
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
Frank Wilhoit: “Conservatism consists of exactly one proposition …There must be in-groups whom the law protects but does not bind, alongside out-groups whom the law binds but does not protect.”
We never have had a president* so completely deserving of scorn and yet so small in the office that it almost seems a waste of time and energy to summon the requisite contempt
I opened a old project and some source files with VS .
If the files was written with Windows characters eg. "Windows: Western"
an alert said that this file is now restored.
But the characters with codes above x7f are marked as unknown characters.
Do somebody know a tool to convert such files to Unicode without loss of the meaning of such characters?
I usually just simply open them in vanilla notepad and check what encoding it autodetected. This autodetection isn't perfect though, but still one of the best.
VS also has an autodetect built in. I don't know how it works though.