aspsupport Release Rss Feed

RELEASED: Simple ASP.NET Profiles Example (Feb 22, 2008)

Fri, 22 Feb 2008 21:07:23 GMT

I've recently been corresponding with a few developers new to ASP.NET who are struggling with storing personal information in an ASP.NET membership application. I've encouraged these folks to adopt the use of ASP.NET Profiles instead of trying to reinvent the wheel.

In an attempt to prove to them how easy it actually is, I created a simple app that demonstrates how you can store information along with a membership user. The complete website is attached.

One thing to note since it's not immediately intuitive; Profile properties are defined in the web.config file. Once you add new properties, you'll need to build the website for them to be "seen" in IntelliSense.

Jim

CREATED RELEASE: Simple ASP.NET Profiles Example (Feb 22, 2008)

Fri, 22 Feb 2008 21:07:23 GMT

UPDATED RELEASE: Create dynamic assemblies in a different AppDomain (Jan 29, 2008)

Tue, 29 Jan 2008 21:35:53 GMT

Here is some code that I created to allow dynamic assembiles to be created in a different AppDomain. This is documented more at [url:http://blogs.msdn.com/tom/archive/2007/12/05/dynamic-assemblies-and-what-to-do-about-them.aspx]

This is important because assemblies don't unload, so if code creates dynamic assemblites in the ASP.NET AppDomain, it will eventually run out of memory because the number of assemblies will grow indefinately.

{{
using System;
using System.Reflection;
using System.Reflection.Emit;

namespace AppDomainCreation
{
/// <summary>
/// Summary description for AppDom.
/// </summary>
public class AppDom : MarshalByRefObject
{
public AppDom()
{
}

public void DoIt()
{
int i = 0;
try
{
for (i = 0; i < 100; i++)
{
AppDomain myCurrentDomain = AppDomain.CurrentDomain;
AssemblyName myAssemblyName = new AssemblyName();
myAssemblyName.Name = "TempAssembly";

// Define a dynamic assembly in the current app domain.
AssemblyBuilder myAssemblyBuilder = myCurrentDomain.DefineDynamicAssembly(myAssemblyName, AssemblyBuilderAccess.Run);

// Define a dynamic module in this assembly.
ModuleBuilder myModuleBuilder = myAssemblyBuilder.DefineDynamicModule("TempModule");
}
}
catch (Exception ex)
{
throw ex;
}
}
}
}
}}

And the code to use it:

{{
private void button1_Click(object sender, System.EventArgs e)
{
myDom = AppDomain.CreateDomain("MyDom");
AppDom my1 = (AppDom) myDom.CreateInstanceFromAndUnwrap(
Assembly.GetAssembly(typeof(AppDom)).Location, typeof(AppDom).FullName);

my1.DoIt();
}

private void button2_Click(object sender, System.EventArgs e)
{
AppDomain.Unload(myDom);
}
}}

CREATED RELEASE: Create dynamic assemblies in a different AppDomain (Jan 29, 2008)

Tue, 29 Jan 2008 20:14:25 GMT

Here is some code that I created to allow dynamic assembiles to be created in a different AppDomain. This is documented more at [url:http://blogs.msdn.com/tom/archive/2007/12/05/dynamic-assemblies-and-what-to-do-about-them.aspx]

{{
using System;
using System.Reflection;
using System.Reflection.Emit;

namespace AppDomainCreation
{
/// <summary>
/// Summary description for AppDom.
/// </summary>
public class AppDom : MarshalByRefObject
{
public AppDom()
{
}

public void DoIt()
{
int i = 0;
try
{
for (i = 0; i < 100; i++)
{
AppDomain myCurrentDomain = AppDomain.CurrentDomain;
AssemblyName myAssemblyName = new AssemblyName();
myAssemblyName.Name = "TempAssembly";

// Define a dynamic assembly in the current app domain.
AssemblyBuilder myAssemblyBuilder = myCurrentDomain.DefineDynamicAssembly(myAssemblyName, AssemblyBuilderAccess.Run);

// Define a dynamic module in this assembly.
ModuleBuilder myModuleBuilder = myAssemblyBuilder.DefineDynamicModule("TempModule");
}
}
catch (Exception ex)
{
throw ex;
}
}
}
}
}}

And the code to use it:

{{
private void button1_Click(object sender, System.EventArgs e)
{
myDom = AppDomain.CreateDomain("MyDom");
AppDom my1 = (AppDom) myDom.CreateInstanceFromAndUnwrap(
Assembly.GetAssembly(typeof(AppDom)).Location, typeof(AppDom).FullName);

my1.DoIt();
}

private void button2_Click(object sender, System.EventArgs e)
{
AppDomain.Unload(myDom);
}
}}