.NET Programming Blog

How to enable Network Level Authentication for Remote Desktop on Windows XP

2010-07-03T20:22:00Z

When connecting to a Windows Server 2008 or newer remote host using remote desktop, you get an error saying that "The remote computer requires Network Level Authentication, which your computer does not support."

To enable Network Level Authentication (NLA) on Windows XP you need to do the following:

Install Service Pack 3
Click Start->Run, type regedit and then press enter
In the left pane, navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
In the right pane, double click "Security Packages", this brings up a dialog box to modify the values, leave all existing values as they are, and at the end of the list add "tspkg", and click OK.
In the left pane, navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders, and in the right pane double click SecurityProviders, and in the dialog box, add "credssp.dll" to the end, be sure that if the list that is present currently is separated by commas, that you add a comma to the value immediately before the "credssp.dll" that you just added. Click OK to save your changes.
Exit the registry editor and restart your computer.
Reattempt your remote desktop connection.

How to edit the password policy on Windows Server 2008 R2 with Active Directory

2010-07-03T19:14:00Z

When setting up a new Windows Server 2008 server either with or without Active Directory you will discover that it has a rather strong policy for passwords. If you are setting this up at home or in a small business environment and don't want to deal with the complex passwords that are required to meet the policy guidelines, you can edit the policy to disable the complexity requirements. You can try going to a command prompt and typing 'gpedit.msc' then navigating to Computer Settings\Windows Settings\Security Settings\Account Policies\Password Policy\ section.

Here you will see the 'Password must meet complexity requirements' item. When viewing the properties of it, usually the Enabled/Disabled radio buttons will be grayed out and you cannot change the values. If they are able to be changed, go ahead and do it, and save out of the dialog boxes. If it is grayed out and you cannot change it here, this is how you do it:

Go to a command prompt
Type 'secedit /export /cfg c:\local.cfg' and hit enter
Using notepad, edit c:\local.cfg
Look for the line "PasswordComplexity = 1" and change it to "PasswordComplexity = 0"
You can also edit "MinimumPasswordLength = 7" to a lesser value if you like.
Save the file
At a command prompt type 'secedit /configure /db %windir%\security\local.sdb /cfg c:\local.cfg /areas SECURITYPOLICY
This will apply the new settings and refreshing the gpedit.msc should reflect the new settings
Set your new less complex password!

How to Get Started With ADO.NET Entity Framework 4 and Visual Studio 2010 (Beta 2)

2010-01-31T23:03:00Z

Introduction

The upcoming release of the .NET Framework version 4.0 and the simultaneous release of Visual Studio 2010 comes with a host of upgrades to the Entity Framework. The Entity Framework is Microsofts officially supported Object Relational Mapping (ORM) tool used to connect .NET based applications and websites to the databases that run them. It provides strongly typed access to the underlying tables and comes with full integration with LINQ. The goal of this post is to help you get your feet wet with a step by step tutorial on the Entity Framework 4 and integrating it with a simple ASP.NET based web application.

What you will need to get started to follow along with this tutorial on your own and to use the associated code download:

Download and install the Visual Studio 2010 Ultimate Beta 2 release, and do a full install.
SQL 2008 Express installed locally on your development workstation
The optional code download of this project

Getting Started

First, open up Visual Studio and click on File -> New -> Project, select "ASP.NET Web Application" and name it EntityFramework4Test, and click OK. This will create a very basic web application with all of the references that we need already set. The project will open to the source view of the Default.aspx page, with some stub code that Microsoft puts there by default. Go ahead and clear out everything inside of the <asp:Content ID="BodyContent"....> tag. We will be back here in a moment.

Next, right click on the EntityFramework4Test project in the solution explorer (the line directly below "Solution 'EntityFramework4Test' (1 Project) at the top), and click Add -> New Item. From this dialog window click on Data in the left pane; this will filter down to a shorter list of items, from this list select ADO.NET Entity Data Model, name it Demo.edmx and click Add. The next window will ask "What should the model contain?" and give you the choice between "Generate from database" and "Empty Model". Select Empty Model and click Next. The next screen will ask which data connection to use. We'll name our database here Demo, so if you have a Demo database that you are already using, just substitute what ever name you like for Demo. Set up a new connection to this database and if it needs created, let the process create it. When it is done, it will bring up the Demo.edmx designer window with a blank slate.

Creating the Entities

Right click on the blank designer and click Add -> Entity... leave all of the fields in their default state, except for the Entity Name field, let's fill that out with "Person". When we do this, notice lower down on the dialog window, the "Entity Set" field.. it automatically types with you and pluralizes the word for you. In this case, its "People" - this is the property by which we will later refer to a Collection of Person objects. Click OK, and the entity will be added to the designer. Repeat this process and add an entity named Group.

Since these entities will refer directly to database tables, we need to construct them in a manner consistent with how we design tables. The entities by default have a primary key defined on them called "Id"; however these fields are not automatically marked as identity. Right click on each of the Id fields, select Properties and in the Properties window, look for the field labeled "StoreGeneratedPattern" - this will indicate that the Store (data repository, i.e. database) will generate this value and that we do not need to be concerned with setting this value.

To add columns to the data entities, right click on them (note: right clicking on different areas of the Entity will give you different context menus, for this part, right click on the top of the Entity and Add should be the first context menu item. When you find the Add menu item, select Add -> Scalar Property. It will add the field to the entity and allow you to change the name; after you name it, you can right click on the property field and select "Properties" and change the Type to what ever is appropriate for the field we're adding.

Add the following fields to Person:

FirstName - give it a type of String
LastName - give it a type of String
EmailAddress - give it a type of String
DateCreated - give it a type of DateTime

Add the following fields to Group:

Name - give it a type of String
DateCreated - give it a type of DateTime
Description - give it a type of String

Next, right click on the canvas again, and select Add -> Association; since we only have two entities right now, the the Entity: drop down will already be populated with each of the entities. Make sure that the Multiplicity: drop downs both have * (Many) selected. This will allow this to be a Many to Many association. We now have the basic data model setup for us to use, and we just need a database to back it all up.

Right click on the canvas again, and select Generate Database from Model and click Finish; this will bring up a T-SQL Editor window with the code necessary to create the schema. The only change we should make alter the behavior of the foreign keys on the PersonGroup table. The last line of the last ALTER TABLE statement is the one we want. Change the ON DELETE NO ACTION ON UPDATE NO ACTION to ON DELETE CASCADE ON UPDATE CASCADE.

This will automatically clear the records from the PersonGroup table when we delete rows from either Person or Group and prevent errors from being thrown or records being orphaned. Hit CTRL+SHIFT+E to execute the SQL, it may prompt you to connect to the database server, if so go ahead and do so. Provided it returns a message that the Command(s) completed successfully, we are now ready to use our Demo database.

Note: If you are running the downloaded project, you will need complete this step yourself - my project assumes that you are using SQL Server Express 2008, and not a file based SQL Server Database.

Accessing the Data from ASP.NET

Now that our entities are set up and the database and tables are created, let's open add a new Web Content Form to our web project. Call it AddPeopleAndGroup.aspx and click OK. Inside the Page_Load method, past the following code (or reference the download project):

//DemoEntities is the Type created that

//is the context to the database.

using (var context = new DemoEntities())

{

//let's create two people that we can add to a group

Person me = new Person()

{

FirstName = "Ryan",

LastName = "Crowley",

EmailAddress = "dontspamme@gmail.com",

DateCreated = DateTime.Now

};

Person you = new Person()

{

FirstName = "Your",

LastName = "Name",

EmailAddress = "dontspamyou@gmail.com",

DateCreated = DateTime.Now

};

Group ourGroup = new Group()

{

Name = "Our Group!",

Description = "Our Group Description!",

DateCreated= DateTime.Now

};

//Add the people to the group

ourGroup.People.Add(me);

ourGroup.People.Add(you);

//Now add the newly created Group to our table of Groups

context.Groups.AddObject(ourGroup);

// this is the method call that will

// persist the entire set of objects to the database

context.SaveChanges();

}

Running this code won't output anything to the screen of course, but it will illustrate the simplicity of adding records to the database. If we now go and select from all of our tables, we can see the data that we just saved. Now, on to reading that data back out and displaying it!

Reading The Data

Let's go into the Default.aspx file and add a GridView with the ID of "gvGroups" and one with the ID of "gvPeople", and leave everything else default - this will let the GridViews auto generate the column names.

Now let's open up the Default.aspx.cs and paste the following code into it (again, or reference the download):

using (var context = new DemoEntities())

{

gvGroups.DataSource = context.Groups;

gvGroups.DataBind();

gvPeople.DataSource = context.People;

gvPeople.DataBind();

}

Voila! Running this will display two grids: one with the group that we just created and one with the people we just created.

That's all for this tutorial. Soon there will be more examples posted as well as a series involving the construction of a more complex, fully functional application.

ASP.NET MVC 2 and Html.RenderAction not working in Visual Studio 2010 Beta

2010-01-22T05:29:00Z

So this week I've been working on an ASP.NET MVC 2 application and am using VS2010 Beta, and was stumped when Html.RenderAction() didn't exist! Documentation everywhere indicates that it did in fact become part of the main MVC product, but why does it not exist?

Well, it does, but it appears to have been moved... though I am not quite sure why this hasn't been documented or even yet referenced anywhere online.

At first I had registered the Microsoft.Web.Mvc namespace in my web.config.. nothing..

Registered, imported and otherwise used fully qualified paths to Microsoft.Web.Mvc directly in my Master page. Still nothing.

After 2 days of digging around for this, and coming up empty handed... I went to the source.. CodePlex.

I downloaded the source for ASP.NET MVC 2 Futures and did a solution-wide search for RenderAction, and found it in the ViewExtensions class in the Microsoft.Web.Mvc namespace. Formerly, the method signature was Html.RenderAction("Action", "Controller",somethingElseHere)

Now it seems to require an HtmlHelper object to be passed in as the first argument... so, I've found that I needed to call it like this:

<% ViewExtensions.RenderAction(this.Html, "Menu", "Nav", new { highlightCategory = ViewData["CurrentCategory"] }); %>

Et voila!

How to use the Namespace Alias in .net 3.5

2009-02-23T19:21:00Z

Recently in one application I am working on, there was a ambiguous reference between two namespaces. One was an object that was generated by our ORM tool (EntitySpaces), and one that was in the System.Web.Security namespace. The class in both was Roles; a namespace alias was the perfect way to resolve this. Setting a namespace alias is easy, in the using section do this:

using WebSec = System.Web.Security;

Then in the code where you have the ambigous reference, just use the WebSec namespace as shorthand like so:

_groupRoles = _orgManager.GetAccessGroupRoles(groupid, WebSec.Roles.IsUserInRole("SystemAdmin"));

.. and that's it!

How to set a date format in a gridview control in asp.net

2009-01-11T02:37:00Z

Have you ever wanted to display a datetime value in a gridview, with a specific format? It doesn't always work intuitively because the <asp:BoundField> uses HtmlEncoding by default to prevent cross site scripting ( as referenced here ), so DateTime formatting techniques using the "DataFormatString" attribute of the BoundField will not work. Fixing this is fairly straight forward thoug, all you need to do is either

1.) Turn off HtmlEncode for the BoundField

2.) Use <asp:TemplateField>

Here is an example using the technique to turn the HtmlEncoding off:

<asp:BoundField

DataField="EndDate"

HeaderText="End Date"

DataFormatString="{0:M-dd-yyyy}"

HtmlEncode="false" />

Here is an example using the <asp:TemplateField> method:

<asp:TemplateField HeaderText="End Date">

<%# DateTime.Parse(Eval("EndDate").ToString()).ToShortDateString() %>

</ItemTemplate>

</asp:TemplateField>

How to access a control on a Master Page from an ASP.NET page using the Master Page

2008-11-13T23:47:00Z

Today I had to figure out how to access a label control on the masterpage my page was using. It isn't quite as straightforward as one might imagine, but still not difficult. For this, I am using C# 2008 (v3.5)

For this particular page, I have an <asp:Label/> control on the line immediately following the <form> tag in the master page. This label is going to be used for displaying general messages, errors, warnings, etc from within the code of pages using it. The problem is that you cannot just do something like "this.Master.FindControl("LabelDisplay").Text = "Some Text Here"; (At least not yet).

To find it you need to walk back up inheritance chain from your present location, to the page that has the control, then find the reference to the target control, cast that reference as the appropriate type (in this particular case Label), then you have access to all of its properties and methods.

Here is the code to do this:

((Label)this.Master.Controls[1].Controls[1].FindControl("MessageDisplayLabel")).Text = "here we are";