The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
I have been searching for MONTHS on how to host SignalR in IIS. I don't want to know how to set up the server side component.. I want to HOST it in IIS. I spent 5 more hours today Googling and trying examples... Wasted day.
SignalR seems to be MS's new web hosting technology, and it's promising. It seems to be exactly what I'm looking for... but it means nothing if I can't host it.
Now there are LOTS of example of Self Hosting (Run in a console app on your DEV pc), and even fewer examples of hosting in a Win Service. Yet for the life of me I can't find a single example of HOW THE ELEPHANT DO YOU SET IT UP IN IIS!!!
This is the reason why I'm usually turned of about web programming.. There are way too many technologies to deal with. With Windows I can code, copy & paste the EXE, and VOILA!! It runs. I know it's not quite that simple, but you get the idea.
Isn't it time for the industry leaders (MS, Apple, etc) to make things EASIER instead of progressively harder? It's days like this that make me wanna hang up my keyboard and retire.
While I am almost certain you have already perused this: [^], I'll mention it ... just in case.
«There is a spectrum, from "clearly desirable behaviour," to "possibly dodgy behavior that still makes some sense," to "clearly undesirable behavior." We try to make the latter into warnings or, better, errors. But stuff that is in the middle category you don’t want to restrict unless there is a clear way to work around it.» Eric Lippert, May 14, 2008
Listen, this is a perfect time, and example, of when to fork out the $$ and call Microsoft for help. If this means that much to you and your operation/project, complaining here, with no other action on your part, is not going to solve your problem...not that we don't like hearing about your issues. J/K.
SignalR seems to be MS's new web hosting technology
Kevin Marois wrote:
I want to HOST it in IIS
Lord, why? I've found IIS to be an interesting experience. Different versions, different control panels. A straight forward setup on one machine totally fubars on another. etc.
I got annoyed enough with the constant changes to MS web tech (ASP.NET, Razor, EF, MVC, MVVM, whatever), that nowadays, I just use my own web server implementation. Of course, that doesn't usually fly in a corporate environment where the edict (and familiarity) is with MS tooling, but for my own stuff, I am happy to live in my alternate universe.
We ended up doing the same thing. We don't get email notifications for every brain fart the site runs into, just the most severe.
I really have to overhaul the email system anyway. There's a ton of notification subscriptions the system supports as well as site errors. In the overhaul I'm going to split out the site errors from everything else and handle it with a different, very simple, subsystem. The remaining subscription emails will be handled by message queuing and an email system running as its own process.
I wish I had the time to do it that way before launch but we had to launch the site 6 months earlier than planned.
You find out the hard way that your email notification code better be rock-f***in'-solid before you launch the site.
Yeah, and with the vagaries of the email server, the only way to really do that is wrap the whole thing in a try-catch that handles its own errors -- I have a UDP message to PaperTrailApp for those super critical help help help! problems.
It looks cool, though it appears to be cloud-based logging and aggregation?
Damn it! I can't use it. Security would throw an epic temper tantrum.
It took SIX MONTHS of thrashing those guys to get authorization to have a 3rd-party stand up TWO SERVERS in Azure to be managed by that company and we would install a client app on a dozen machines that connects to them and feeds them data all day for analysis. And that wasn't even HIPPA regulated nor business critical stuff either!
They're heads would explode if I showed them this thing.
I was hoping (and still am) that this was going to be a 'well, ironically, having made an attempt at writing a HAL in Python, the kiddies have discovered that they can't do it, and have come to me cap in hand to help them'
having made an attempt at writing a HAL in Python, the kiddies have discovered that they can't do it, and have come to me cap in hand to help them'
First part happened, second part has not.
Now they're writing it in F#, because one of the kiddies as a Haskell background.
The irony here is:
1) very few people actually know F#, so the code will undoubtedly be thrown away by the next iteration of kiddies, if not sooner.
2) it's like reading imperative code with match statements instead of switch and type instead of enum, and everything is mutable.
3) FP is just the wrong approach for this kind of work because you're dealing with a lot of struct stuff for the hardware, a lot of mutable data from the I/O, and possibly the need to maintain some sort of state information, like is the hardware up or down since the last time we checked.
4) from what I've seen so far, no logging, no exception handling, no modularity, and a lot of hard coded constants and strings, but hey, "we're ahead of schedule!" is pronounced loudly and proudly at every stand up.
Oh nice, give the old bastard who has spent years being nitpicked by QA a shot at your first UI
I must admit, I took great sadistic pleasure in the process.
Mycroft Holmes wrote:
but what a bunch of pedantic, anally retentive, irritating, annoying and bloody persistent sods they are.
Yeah, aren't they wonderful? Honestly, once I started to learn how to work with QA (part of which was, don't rely on them accurately telling you what they did to break your software), I started enjoying the process, because it did improve the quality of the product, as well as my code and I learned better architecture (ok, fancy word for automatic logging) as well as a result of my QA experiences. The best thing though was when we got to a point of working together, and I could ask them "I found this weird bug in my code and I can't figure out how to reproduce it, could you try?" That was great.
In our little system we have email sending configured as a Boolean. Down when we're instantiating the class that sends the email, we look at that. If false, we instantiate an implementation of the class which writes to a local file instead of sending the email.
So, we can check content etc in development without the risk of "oops that was a real email address."
I wonder if something similar could be wired up for your error condition. Once you're in the catch block, fire off the email send, but pass the magic param which says "write to log/file/send up a flare/whatever."
I did something similar. My program connects to a SQL database and when that database connection is broken an exception is thrown and logged to a message processor which also tries to log it to the, wait for it, SQL database. Which then throws the exception again.....
Not exactly his area of expertise, but he's right. You could see a living cell as a very complicated biochemical machine. Everything that can directly modify the DNA or interfere with its replication can eventually cause cancer.
"I don't know, extraterrestrial?"
"You mean like from space?"
"No, from Canada."
If software development were a circus, we would all be the clowns.
you have to die from something - shortness of breath, whatever - you can be the healthiest person in the world and get hit crossing the street (or these days, get an lead injection from some maniac with a gun) ... so you may as well do everything in moderation, enjoy, be a nice person, and not beat yourself up