Visual Studio 2015 is out
-
Do you trust a repro'd Microsoft bug report?
-
-
Yes, and all of those people need a swift slap upside the head.
the users, and a lot of businesses yes, but what about that company that's running XP because they have a 16 bit piece of critical business infrastructure that's so old that they don't have the source code for it, and even if they did there's no compiler that could produce 32 or 64 bit code for it, and they're trying to rewrite it but all the documentation of the business rules is missing so they're having to reverse engineer the thing, and they've been working on this for years but the thing is so fiendishly complicated they are still years away from finishing the rewrite.
what about them? do they need a swift application of the cluebat?
-
-
that's assuming that it's capable or running on Windows 7
I know there's at least one company out there in that boat because my first task as an intern back in the early days of W& was "hey, see if you can get our build process running on a windows 7 box. Here's the binder of what we know about the build system, see what you can do."
took me the better part of two months and i lost track of how many wipe/reinstalls before i got pulled off the system. the build process involved 5 different languages, and was glued together with about eighty batch files and seemingly relied on two incompatible versions of some DLL that had to go in the GAC, but if you installed things in the right order (including windows updates) you could get one of those versions to recognize that there was a different version in the GAC and load from a local copy instead.
that was, thankfully, the worst build system i've ever had to work with before.
-
2) I do not trust random people on Stack Overflow.
Eh? That blog post was one of SO's own devs speaking...
-
You mean the people who brought us Discourse?
YES OBVIOUSLY MASTER SKILLED SOFTWARE DEVELOPERS!!!
-
what about them? do they need a swift application of the cluebat?
Yes, and the cluebat has "run 32-bit Windows 7" on it, duh. I'm in that boat myself.
-
that was, thankfully, the worst build system i've ever had to work with before.
It's almost like the universe was trying to tell people they were Doing It Wrong.
-
Yes, and the cluebat has "run 32-bit Windows 7" on it, duh. I'm in that boat myself.
as i said leater. if that's an option
It's almost like the universe was trying to tell people they were Doing It Wrong.
well the build system did grow over the at the time 25 year lifetime of the product.the built product ran perfectly fine on 32 and 64 bit computers, but the build system was so creaky and convoluted that it could only be built on that one desktop computer....
and yes, they were working on getting to a sane buildsystem, but the process was pretty slow. i have no idea if they eventually managed ot or not. they certainly hadn't by the time VP politics at home office caused them to close our branch office and move the project to seattle.
-
our app is so old, parts of it would still run in dos. We have ini files in the Windows folder, because back then that seemed like a good idea. But somehow we have a compiler that somehow converts it old evil language and generates wpf windows from it. I never want to know how they got that working...
-
You mean the people who brought us Discourse?
I think the overlap between those two groups consists of Jeff and Jeff only.
You can pin a lot of things on SO devs, but Discourse? That's harsh, man.
-
I think the overlap between those two groups consists of Jeff and Jeff only.
Didn't Sam's resume include some time with SO?
Edit: Yes.
-
In it's current incarnation this blog is implemented as a Discourse plugin
....Because he could?
-
....Because he could?
hmm... interesting concept actually.
i think it's even doable.
/me muses about doing the same
-
We should turn it into something way more interesting than a blog....
Maybe some kind of MMO? ;)
-
now there's an interesting idea....
-
It could be like skyrim, where you're walking along, and then suddenly get jellypotatoed 50 feet in the air!
-
And the loveable Sam. The loveable, yet still completely incompetent, Sam.
You can pin a lot of things on SO devs,
I'm still pissed about their moronic obsession with the useless and obviously-flawed OpenID login system.
-
well the build system did grow over the at the time 25 year lifetime of the product.
At some point, every few years, someone should've sneaked in some time to try to improve bits and pieces of it, is all I'm saying.
Because
the build system was so creaky and convoluted that it could only be built on that one desktop computer
when you're in this situation, and that computer dies, oops. I worked at a place where if one server died, it was time to shut and lock the doors, and see who you could sublet the office to for the rest of the lease. (And this wasn't a small business, btw, but a company with 8-figure annual revenue.
-
At some point, every few years, someone should've sneaked in some time to try to improve bits and pieces of it, is all I'm saying.
should have. didn't and i joined at year 23.
when you're in this situation, and that computer dies, oops.
more than just oops more liketime to shut and lock the doors, and see who you could sublet the office to for the rest of the lease.
this
-
I'm still pissed about their moronic obsession with the useless and obviously-flawed OpenID login system.
The only real benefit is that it greatly reduces the amount of information that they have to keep completely secure.
But then it could have been worse. It could have been Shibboleth.
-
The jokers from the PRISM library have taken this exact timespan to do their vacation.
"Oh, what are you saying? A new version of .NET and a new version of Windows will be released inside a week? Whelp! Let's take a vacation and make sure that none of our samples are working!"
Good thing Github offers the version history of even the landing page or I wouldn't even have known when they began their vacation - I mean, just stating "We'll be taking a vacation over the next weeks" without offering some hint as to when your vacation begins...
And the other MVVM framework I looked at (MvvmLight) has a documentation that's beyond belief. It consists of several videos (some of those you have to pay for) and several "What is mvvm?" type of blog entries and further videos.
Why are those guys pathologically incapable of offering something like: "If you want to use this feature you'll need to do this at the minimum!" - no, it's always a "We'll show you everything we're capable of, up to and including the kitchen sink!"
-
The jokers from the PRISM library
samples ... working!"
Dude, these guys are also responsible for Infragistics. I can make the IG demo apps crash with nothing but my mouse and the shift key. They're horrible.
Seriously, go find my thread and use my MVVM stuff. It will work. Mod it if you need more stuff.
-
Infragistics.
They're horrible.
Sponsor Announcement: Infragistics
A few months back, Alex announced our sponsorship program. This has been a great partnership that’s helped us bring you our regular content, but also special features like TDWTF: Live. We’re proud to introduce our second sponsor: Infragistics
Just saying...
-
I know. I complained about them there too. It's cool when they decide to give your site money, but I can only really recommend them if you need an editable pivot grid in WPF. And at that point, Cthulu already has his tentacles through your skull.
-
Though I have to say that the new NuGet packet manager seems way more usable than the old one.
-
-
It's in some way different now?
-
Indeed. See for yourself.
-
Ah, right, it's not modal now. That's the only one I've used for more than a month, so I was shocked to see how it worked in 2013 just now.
-
Little problem: The Remote Debugger simply doesn't do anything. Building and deploying an app always results in the app running on the local machine, instead of the remote one.
No errors, warnings, nothing. Already tried all the options regarding authentication, architecture and whatnot.
I mean, when I first select the "Remote Machine" option, it detects the Remote Debugger instance just fine and seems to accept it. It's just when I run the whole thing that it plops up on my main screen.
-
what about them? do they need a swift application of the cluebat?
They need a VM with differencing disks, externalized isolated storage of application data heavily vetted and scrutinized and a nightly reset policy on the VM.
-
but what if the application needs to talk to a piece of specialized hardware that can't be virtualized?
what about then? you can't virtuialize the machine then!
-
They need a VM with differencing disks, externalized isolated storage of application data heavily vetted and scrutinized and a nightly reset policy on the VM.
Good luck getting a VM that can bit-bang a parallel port accurately....
Filed under: when rewriting half your program to run on an Arduino is a good idea...
-
parallel port
Oh God, I remember that one project that had us drive a robot from a parallel port. Turns out, finding a laptop that runs MS DOS 6.22 natively is not an easy task...
-
Oh God, I remember that one project that had us drive a robot from a parallel port. Turns out, finding a laptop that runs MS DOS 6.22 natively is not an easy task...
If you can boot from a usb floppy, you can still (last I checked) get DOS from bootdisk.com.
-
DOS causes cancer, you insensitive clod!
And yes, parallel and serial ports were a bitch to deal with under DOS and Windows (each version it's own hell, from 16 bit to 32 bit).
-
I remember that one project that had us drive a robot from a parallel port.
Yowch! These days it would be easier to just staple some extra hardware to it so you can talk via BT or wifi…
-
And yes, parallel and serial ports were a bitch to deal with under DOS and Windows (each version it's own hell, from 16 bit to 32 bit).
Oh God. The nightmares have finally stopped from dealing with the COM (modem) api on Win32s. Don't bring those back! (the api was only available on the 16-bit side of the world. We were in 32bit. Thunks. :shudder:)
-
Thunks. :shudder:
Nah, it was really simple! You just needed a shim DLL, a special compiler, write a script, get a macro assembler...
The parallel port was nice to use though. Even if it wasn't a bi-directional port you had at least 8 bits in and out available which made it really fast to do simple computer control of something. Now I have to have a little micro as a USB slave and then shout at the HID library for a while (device code 10, yay).
-
It's actually a fair pain in the dick. IT is all "NOPE WE DON'T SUPPORT THAT SOFTWARE AND WE AREN'T GOING TO CREATE AN EXEMPTION IN THE PROXY RULES BECAUSE REASONS"
So I have to add the farking MITM certificates to the certificate store for every app that cares (it's a fortunately small number). Assuming the vendor has been kind enough to allow some manner of access to that certificate store.
Unsure why VS isn't using the same certificate store IE uses. That would make way too much sense. Haven't figured it out yet.
-
IT is all "NOPE WE DON'T SUPPORT THAT SOFTWARE AND WE AREN'T GOING TO CREATE AN EXEMPTION IN THE PROXY RULES BECAUSE REASONS"
Ah, so it's all “no VS for you, haha!” then?
Unsure why VS isn't using the same certificate store IE uses.
Haven't they switched to using a system-wide security store yet?
-
Finally got around to playing with this for a few minutes last night.
Finally, the 30-day developer licence thing has gone (although this could be down to Windows 10 and not VS2015).
The way of creating apps for desktop and phones has been simplified (again) which is definitely welcome.
There's a handy extension here that I'll be tryng - https://visualstudiogallery.msdn.microsoft.com/5d01e3bd-6433-47f2-9c6d-a9da52d172cc
-
They have one. But third party vendors ignore the fuck out of it. And apparently (but unconfirmed because I haven't had time to mess with it) VS as well.
-
That one looks useful.
-
Okay, remote debugging is now working - I can finally connect to my laptop and deploy the app from my desktop to the laptop.
Bonus: If I set debugging breakpoints I now get the variables in scope - in VS 2013 I only saw an empty stack which made this a bit useless.
On the other hand, whenever I build the solution now, the XAML designer preview crashes with a System.NullReferenceException - but if I click on the "reload" link, it works just fine. Very weird.
Edit: Setting the project to x86 solved the issue.
-
You can have one of mine. IBM T42, complete with built-in parallel port!
-
You can have one of mine. IBM T42, complete with built-in parallel port!
Thanks, but no way I'm doing this shit again.
Fun story: we used Turbo C for the project, but according to our lovely professor, most of our logic was supposed to be done in
asm { }snippets, with C code only providing some structure. So we had a function like this:void do_stuff(unsigned char a, unsigned char b) { asm { //use a and b to set parallel port registers } }and whenever we ran it, it read
afine, butbseemed to always be zero in theasmblock. It read fine outside.We spent like 3 hours debugging, searching, rewriting the
asmblock over and over again - nope. Nothing. Nada. We were totally clutching at straws at this point, so I said "hey, let me try something".void do_stuff(unsigned char a, unsigned char b) { unsigned char c = b; asm { //use c instead of b } }"What? That's a no-op, that doesn't even make sense you re... the fuck, what do you mean it works?"
-
Oh wow, we're truly sorry you had those requirements.
When I took those "beginner level" programming classes, I avoided Assembly until I really had to (I. E. Bit banging during an interrupt).
