Tech.It.2.Me->{By.Anton.Perez} » General Development

Using Visual SourceSafe 2005 with Visual Studio 2010

anton — Fri, 18 Mar 2011 21:07:52 +0000

You may notice that when you attempt to add your solution to a source control in Visual Studio 2010, that it only shows a TFS server as a choice. Don’t be alarmed, however, just:

1. Go to Tools > Options.

2. Click Show all settings if not checked, then go to Source Control.

3. Go to Plug-in Selection, then change the dropdown to Microsoft Visual SourceSafe.

4. That’s it!

Happy Trailing!

Web Service Reference in Visual Studio 2010

anton — Fri, 04 Mar 2011 22:48:08 +0000

If you’ve used Visual Studio 2008 or 2010, you’ll notice that Web Reference is no longer there (like in VS 2005 and previous), instead, you see Service Reference –- actually, it’s STILL there, just hidden!

So, what’s the difference? Well, according to this post:

Add Web Reference is the old-style, deprecated ASP.NET webservices (ASMX) technology (using only the XmlSerializer for your stuff) – if you do this, you get an ASMX client for an ASMX web service. You can do this in just about any project (Web App, Web Site, Console App, Winforms – you name it).

Add Service Reference is the new way of doing it, adding a WCF service reference, which gives you a much more advanced, much more flexible service model than just plain old ASMX stuff.

So, how do you access it? Simple — right-click on Service References in the Solution Explorer window and…

Click on “Advanced…”

Then click on “Add Web Reference…”

Voila! You can now consume the web service like you did pre-Visual Studio 2008 era. Happy coding!

How to configure source control for Visual Studio

anton — Sat, 20 Nov 2010 00:03:36 +0000

Reference for jsSHA

anton — Thu, 29 Jul 2010 02:16:30 +0000

jsSHA - A JavaScript implementation of the complete Secure Hash Standard family
(SHA-1, SHA-224, SHA-256, SHA-384, and SHA-512) by Brian Turek

About
-------------------------
jsSHA is a javaScript implementation of the complete Secure Hash Algorithm family as defined
by FIPS PUB 180-2 (http://csrc.nist.gov/publications/fips/fips180-2/fips180-2withchangenotice.pdf)

With the slow phasing out of MD5 as the standard hash to use in web applications, a client-side
implementation of the complete Secure Hash Standard family was needed. Due to SHA-384 and SHA-512's
use of 64-bit values throughout the algorithm, JavaScript can not easily natively support the calculation
of these hashes. As a result, a bit of hacking had to be done to make sure the values behaved themselves.
SHA-224 was added to the Secure Hash Standard family on 25 February 2004 so it was also included in this
package.

Files
-------------------------
src/sha.js
The complete SHA implementation

src/sha1.js
A smaller/web friendly implementation of only SHA-1.

src/sha256.js
A smaller/web friendly implementation of only SHA-224 and SHA-256.

src/sha512.js
A smaller/web friendly implementation of only SHA-384 and SHA-512.

src/wrapper.js
Wrapper functions to be added to the above script files if the jsSHA 0.1 interface is desired

test/test.html
A test page that calculates various hashes and has their correct values.

Usage
-------------------------
Include the desired JavaScript file (sha.js, sha1.js, sha256.js, or sha512.js) in your header (sha.js used below):

Instantiate a new jsSHA object with your string to be hashed as the only parameter. Then, call getHash with the desired
hash variant (SHA-1, SHA-224, SHA-256, SHA-384, or SHA-512) and output type (HEX or B64). In the example below,
"This is a Test" and "SHA-512" were used as the string to be hashed and variant respectively.

var shaObj = new jsSHA("This is a Test");
var hash = shaObj.getHash("SHA-512", "HEX");

NOTE: If you are using sha1.js, omit the SHA variant parameter as there is only one option.

Since the interface was changed drastically from 0.1 to 1.0, src/wrapper.js is included in case the old interface is desired.
Simply copy and paste the correct functions from wrapper.js to the bottom of the used jsSHA JS file.

Contact Info
-------------------------
The project's website is located at http://jssha.sourceforge.net/

Fix to "The handle is invalid" error when ASP.NET writes to the Eventlogs

anton — Mon, 12 Jul 2010 20:50:19 +0000

Have you ever come across the error below with one of your ASP.NET web apps that is trying to write to the Eventlogs? If so, read on…

By default the ASPNET user cannot access the existing eventlogs categories. To resolve this, you must set the permissions in the Eventlog key in the registry:

Launch RegEdit.
Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\.
From the menu, select Edit->Permissions.
Click the Add button and write ASPNET (if ASP.NET is running under a different User ID, use that ID instead).
Click OK.
Select the newly added user from the list (ASP.NET Machine User by default).
Click on Full Control in the Allow column. 8. Click OK.

More info here.