Scott Hanselman is a former professor, former Chief Architect in finance, now speaker, consultant, father, diabetic, and Microsoft employee. He is a failed stand-up comic, a cornrower, and a book author.
Current Project Command Prompt for VS.NET. Another answer from the VS.NET Info Center Q&A Forum describing how to start a command prompt and the file explorer in the directory of the current project. [sellsbrothers.com: Windows Developer News]
I found this to be a very useful tip. I noticed that Chris appeared to be running VS.NET out of, logically, C:\VS.NET, when the default is C:\Program Files\Microsoft Visual Studio.NET. I ended up using Short File Names ala cmd /k c:\PROGRA~1\MICROS~3.NET\Common7\Tools\vsvars32.bat as no combination of quoted long file names seemed to work.
Great tip though, so I added two external tools, one for the Command Shell in Project Dir and Windows Explorer in Project Dir.
Scott Hanselman is a former professor, former Chief Architect in finance, now speaker, consultant, father, diabetic, and Microsoft employee. He is a failed stand-up comic, a cornrower, and a book author.
Google Weblog: Announcing Froogle! [Brian Jepson's Radio Weblog]
Ah! A competitor for http://www.mysimon.com!
Scott Hanselman is a former professor, former Chief Architect in finance, now speaker, consultant, father, diabetic, and Microsoft employee. He is a failed stand-up comic, a cornrower, and a book author.
I ran all over the Net (via Google and Google Groups) this evening trying to figure out the answer to what I thought was a simple question. Everywhere I turned I found pieces of what I wanted to do...clues...but not even close to the whole solution (isn't that always the way?). So, when I DID figure it out (for better or worse) I wanted to put the solution out in the world, lest I forget it, so if some poor schmoe needs to go looking for it him/herself.
I've got a very constrained environment in this instance, with ASP (not ASP.NET) on the client side, calling a Java WebService that includes a Base64 encoded image. I wanted to get the image out of the soap envelope WITHOUT touching the disk. The data in the image is very sensitive and it can't be saved.
I know this is easy, and done basically automatically with serialization in ASP.NET...heck, most SOAP stacks handle this kind of stuff for you...I guess I just made it harder than it needed to be in Classic ASP. I found all sorts of interesting stuff, including an online Base64 decoder, and one guy who actually wrote a BASE64 Decoder entirely in VBScript (which was, not surprisingly more effort than I was willing to handle today)!
The Proof of Concept result is this snippet of ASP/VBScript code...sigh...these things are so obvious AFTER they've been written!
<%
Dim mDoc
Set mDoc = Server.CreateObject("MSXML2.DOMDocument")
mDoc.async = false
mDoc.ValidateOnParse = false
'NOTE: The REAL xml file will come from inside our SOAP Envelope when it comes over from the SOAP/REST call to the Java WS
mDoc.Load Server.MapPath(".") + "\\sample.xml"
Dim oNode
Set oNode = m_Doc.selectSingleNode("/Envelope/Body/ImgQryRs/imgBin64")
'NOTE: I had to force the dataType to bin.base64 since there wasn't yet an XSD available to declare it was so.
oNode.dataType = "bin.base64"
Response.ContentType="image/JPEG"
Response.BinaryWrite oNode.nodeTypedValue
%>
Interesting things about this:
Scott Hanselman is a former professor, former Chief Architect in finance, now speaker, consultant, father, diabetic, and Microsoft employee. He is a failed stand-up comic, a cornrower, and a book author.
http://www.tinyurl.com - a simple (even REST-ful) solution to a big problem. It's helped me many times. Check it out.
Scott Hanselman is a former professor, former Chief Architect in finance, now speaker, consultant, father, diabetic, and Microsoft employee. He is a failed stand-up comic, a cornrower, and a book author.
Disclaimer: The opinions expressed herein are my own personal opinions and do not represent my employer's view in any way.