I'm going to start off by saying that if you plan on buying ANY NetGear switch with the purpose of using as a reliable VPN, DO NOT. NetGear no longer supports the VPN Client software used to connect to it via IPSec and it is instead using TheGreenBow Client IPSec software set. While the software is ok, the interface is cludgy and definitely designed with more tech savy people in mind and is not a good interface used for business purposes. In short, the NetGear switches and firewall's work ok unless you plan on using it for VPN purposes, there are many many other options out there that have better interfaces and more professional VPN setup.

If you choose to purchase it anyway, or have already purchased it, feel free to check out this blog post to help get it configured: http://www.dotnetdawgs.com/post/Netgear-PROSAFE-VPN-Client-Configuration.aspx

CREATE FUNCTION [dbo].[udf_GetUpdatedColumns]( 

@Tablename VARCHAR(100), @ColumnsUpdated VARBINARY(255) ) 

RETURNS TABLE 

AS 

RETURN 

    SELECT 

        COLUMN_NAME 

    FROM INFORMATION_SCHEMA.COLUMNS Field 

    WHERE 

        TABLE_NAME = @Tablename 

        AND sys.fn_IsBitSetInBitmask( @ColumnsUpdated,

            COLUMNPROPERTY(OBJECT_ID(TABLE_SCHEMA + '.' + TABLE_NAME), 

            COLUMN_NAME, 'ColumnID')) <> 0

Usage is as follows:

ALTER trigger [dbo].[trg_InfoUpdate] on [dbo].[Info] for  update

as

print 'TRIGGAH'

DECLARE @ColumnsUpdated VARBINARY(1000) = COLUMNS_UPDATED()

SELECT * FROM dbo.udfDecodeBitmask('BankingInfo', @ColumnsUpdated)

If you are having as much trouble as I did figuring out where the hell all the web.config settings went after creating Users and Roles using the built in administration tools in .NET then read on!

It turns out, that in ASP.NET 4.0, they removed some of the "clutter" from the web.config since some web.configs were getting very large with configurations and developer added keys etc. So they moved it to a machine.Config file inside of the framework folder. What this means is that they took out all the standard settings in the web.config that are required to run a website so you don't have to see them anymore....HOWEVER, they ALSO moved the default membership provider settings as well. So what does this mean?  It means you can't just make a tweak to the default settings, you need to actually implement your OWN web.config provider as follows:

 <membership>
            <providers>
                <clear/>
                <!--<add name="AspNetSqlMembershipProvider" type="System.Web.Security.SqlMembershipProvider" connectionStringName="ApplicationServices" enablePasswordRetrieval="false" 
                 enablePasswordReset="true" requiresQuestionAndAnswer="false" requiresUniqueEmail="false" maxInvalidPasswordAttempts="5" minRequiredPasswordLength="6" minRequiredNonalphanumericCharacters="0"
 passwordAttemptWindow="10" applicationName="/"/>-->
                <add name="AspNetSqlMembershipProvider" type="System.Web.Security.SqlMembershipProvider" 
connectionStringName="test" enablePasswordRetrieval="false" enablePasswordReset="true" requiresQuestionAndAnswer="false" requiresUniqueEmail="false" maxInvalidPasswordAttempts="500" minRequiredPasswordLength="6" minRequiredNonalphanumericCharacters="0" passwordAttemptWindow="10" applicationName="/"/>
            </providers>
        </membership>
        <profile>
            <providers>
                <clear/>
                <add name="AspNetSqlProfileProvider" type="System.Web.Profile.SqlProfileProvider" connectionStringName="ApplicationServices" applicationName="/"/>
            </providers>
            <properties>
                <add name="DisplayName"/>
            </properties>
        </profile>
        <roleManager enabled="true">
            <providers>
                <clear/>
                <add connectionStringName="test" applicationName="/" name="AspNetSqlRoleProvider" type="System.Web.Security.SqlRoleProvider"/>
                <!--<add connectionStringName="ApplicationServices" applicationName="/" name="AspNetSqlRoleProvider" type="System.Web.Security.SqlRoleProvider"/>-->
                <add applicationName="/" name="AspNetWindowsTokenRoleProvider" type="System.Web.Security.WindowsTokenRoleProvider"/>
            </providers>
        </roleManager>

Now you can go ahead and change the settings as necessary.

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!