For those who may benefit, I discovered the jcarosel jquery plugin, which is great for building menues such as the one I was searching for. /M

Hello all, I'm really keen on the kind of "overview menu" (for lack of a better description) which you can find for example at www.raytheon.com - the one with the big red buttons. Does anyone know if somelike this is available from somewhere? I haven't myself been succesful in my search. I could develop it but surely there must have been someone before me. Many thanks, Morten

That's certainly a valid attempt, I like the outcome of your discussion. Although the "able to detect and correct glaring mistakes" for some reason seems strangely out of place :)

You had both titles at once, on the same line on your card? It's certainly pompous, though still a bit vague, the "System Operator" part. This could be - as I suppose is my basic grudge against the 'developer'-tag - describing anyone from the receptionist to, well, God.

Hello all, I got a bunch of business cards today, and my title simple says 'Developer'. That has become the standard, I guess, at least around here. I did get to wonder, though, when this switch came across: I used to be a 'programmer'. I always thought that fit the bill better, at least it's a more accurate description. "Developer" seems a bit vague, or even pompous. Anyone remember their first programming-related job-title?

Hello folks, I can send an e-mail from my web-server like so:

      SmtpClient mailClient = new SmtpClient();
      mailClient.Send(some defined mail);

I'm however unsure as to the security in this. If someone should gain access to the machine, and it's set up to allow the above, wouldn't this mean the attacker would be able to use the server as a spam-bot? Many, many thanks for your input (and possible a great link explaining the reasoning behind it), Morten

That's rich! :-D I haven't the nerve to be upfront about it, but I suppose I could send him an anonymous gift! :D Good stuff :D

He didn't CC the entire company, thankfully, 'only' my colleagues in the tech-department. I've taken some time - a few weeks - to contemplate the episode, and I'm somewhat weary of taking it up with my boss now that time has passed. I should've reacted sooner, but I was kinda shocked and missed my opportunity. The more I hear from you guys, though, the more I'm convinced there's a valid case for a calm reply such as the one suggested by Mark (and thanks for that!). Thanks for your 2 cents, appreciate it.

Hello everyone, many thanks for your valuable input, I really appreciate it. You've offered a lot of insight. Especially the thing about checking in production connectionstrings, which is a practice here - for no other reason than the small size of the projects. Being practice, I've never considered not doing this, but your arguments to the contrary have made me reconsider. I'll personally implement a test/production environment from here onwards, running my stuff of a local sql server express before moving into production - and do a build which will only run on the production database if the machine is the production server. A valuable eye-opener, which will also ensure I won't run into this sort of mess again. Truly, thanks a lot. /Morten

Hello smcnulty2000, you bring up a lot of valid points, great to learn from. You're of course right, it'll blow over given time. I'm afraid I don't have it in my 35-year old family-man persona to test the game for advanced players scenario you mention, albeit if I'd been 5 years younger... I suspect you're right about the turf thing, he's been aching to go somewhere. A line from a Richard Pryor (methinks)-movie comes to mind, "I never saw a white man in more dire need of a blow***". I'll go home to my darling wife and smiling daughter and feel all the better for not pursuing it further. Politics, man... Not my game. Thanks, Morten

Hey Simon, thanks for your input in this, I did actually know what the code does, I probably didn't clarify this properly in the original post, I did spend time going through it before hitting F5. The unexpected thing was merely a dll which hadn't been compiled - nothing serious, and besides also code I wrote. So I'm not without a clue as to what would happen. I laid the groundwork and not much has changed about the code, I see. I do agree with you - now - that I should've asked him first, I suppose I only didn't because I had no idea it would amount to this sort of an issue. Your suggestion to apologize and bow out is probably the best way to go.

Good on you! Try to bottle some of it, if possible! :-) Well done.

Hey guys, would love your two cents on this. Being the careful guy that I am, I need som pointers to figure out if I've been the victim of a cross over-reaction (my own estimate) or if I should start getting my act together (always a possiblity). The short version: I'm in a minitry of education government stats department. We're three asp.net guys who churn out various web-surveys for the schools to fill out. Recently we went public with one particular survey. Being the ever curious and eager to learn individual, I thought I'd take a look at the code behind it. This is the day after it's gone public. One reason being that I'd recently been put to the task of supporting another guy's project when he was unforseenably away, and I anticipated that situation might creep up again, that I'd have to support this one too. Another reason being that I simply like to look at other people's code, to try and learn something new. In this case, alas, not so much new stuff had gone into it. I say 'new', because I wrote the bulk of the code myself, before a brief last-year hiatus which saw this guy, we'll call him 'Lars', take over. So I export the code from the SubVersion repository. I didn't check it out - only exported it. Any changes won't be persisted back into the repository. And I ran it. Guilty as charged. I took a look at the default.aspx, went a bit further from there, nothing serious, application or server-threatning c# stuff going on here, let's fire this one up and see how it looks... Nope, stops with a error - some server controls dll missing. I had originally authored some server controls to go with the project, but in my youth's inexperience I included these not in a seperate project to be referenced but as stand-alone must-be-compiled-seperately. Would do that differently now, but anyways, I put it down because I had other things to attend to. Alas, the web.config healthmonitoring has dispatched an e-mail to Lars, informing him of the run-time error. And 'Lars' goes ape-shit. He send an e-mail to yours truly, CC three bosses and all of my co-workers, lambasting me for running his code. Heck, I thought all the code we wrote was 'ours'. I'm judged irresponsible (quote "you don't know what you're dealing with, you could've done serious damage to a project in production") for checking out the code (wrong) and running it (true). His argument - and, I suspect, his justification behind CC'ing pretty much everybody I know - is that the crime is severe because the code is in production now. I

Hello, my web-application must run with requireSSL="true" on the web-server. But within my local environment, I use requireSSL="false". Is there a way I can switch this on and off dynamically come deployment? "If (! System.Environemnt.MachinName.Equals("MyLocalMachine")) { ... ? Hope to hear from you, many thanks, Morten

Thank you, everyone, for your insight on this issue. Can I ask you, now, how I should go about optimizing my code for x64 processors? Any links you would recommend would be much appreciated. Many thanks, Morten

Hello Colin, this was also my impression. Thanks a lot for clearing this up for me. best, Morten

Hello, a 3rd party supplier informs me their components are compiled for "ANY CPU", so they'll run x86 or x64 based on the platform to which they're deployed. This confuses me a bit; I had thought a select choice of x64 compilation would ensure the best performance, which is why so many companies these days deliver product-installers for both x86 and x64. But if I'm to take his word for good measure, there's no need (at least .net-wise) to ever compile to a specific CPU architecture, as the "ANY CPU" option will always ensure the assemblies run as fast as possible, given the host CPU? Hope someone might be able to clarify on this, thanks in advance, Morten

You could look into the SlidingExpiration property.

Hello Sir, I once build an application for that purpose. Email me and I'll send you the source code for it. Best, Morten

Hello all, happy holidays, when you get thus far. I'd much appreciate your thoughts on this issue: I need to transfer a bunch of images from a server to a winforms application. Approximiately 30-40 group4fax tiff's at an unknown size. I haven't as yet decided on the architecture. I thought I'd go with a WCF service and transfer the images as byte arrays, pre-loaded to server-memory. Would this procedure seem recommended for this task? The aim, naturally, is to transfer the least amount of bytes to the client, to allow for the best response-time. I've noticed when I convert the images to byte arrays, these arrays triple in size, so I guess that's not the best way to go 'round the issue of limiting the client's download time. All your thoughts are surely appreciated, thanks in advance, Morten