Debug And Fix You

Asp.net MVC 3 & Membership Provider

admin — Wed, 25 Aug 2010 11:45:41 +0000

It’s easy to have the mvc membership provider working with mvc3.

Install VS 2010 express.
Install MVC3.
Create a MVC3 website.
Publish the site to the hosting company’s server via ftp.
Install the membership provider from http://mvcmembership.codeplex.com/
Copy the necessary assemblies from the sample website to your website. The primary dll is mvcmembership.dll
Run the aspnet_regsql.exe and point the destination to your sql database.
Change the membership provider connection string to point to the sql database.

C# Questions

admin — Fri, 20 Aug 2010 11:35:29 +0000

What are the Refactoring tools?
How to transfer an image from one web service to another web service?
Is there a partial method?
How to port digital keys from one system to another?
What are the patterns promote loose coupling?
What are the differences between basichttpbinding and wshttpbinding?
What are the differences between the list view in asp.net 2.0 and 3.5?
What are the new features in .net 3.5?
Why factory pattern is a hindrance to soa?
What is a framework? What are the things to consider when a framework is developed?
Can a temporary table have a primary key?
Can a temporary table be indexed?
When a table is created

Publishing MVC 3 sites with Visual Studio 2010

admin — Sun, 08 Aug 2010 11:41:44 +0000

The other day I have got into problem with publishing an asp.net mvc3 site to a shared hosting provider. The server is Microsoft 2008, but it did not have Front Page installed – any version of Visual Studio 2010 needs to have the Front Page to do the publishing. Here is how to publish a site in a situation like this:

Use the FTP option and create a blank asp.net application on the server. This does not require Frontpage.
Now, turn to the project on the local box. Build the project locally on the box.
Publish the site to a different directory locally.
Copy the whole site – directories, files – to the server.
Copy the System.web.mvc.dll to the bin folder. Please make sure the mvc dll is a mvc3 version.

SQL Performance improvement

admin — Tue, 04 May 2010 04:43:16 +0000

Make sure there are indexes available.
Not too much denormalization. The joins cause performance problems.
Are triggers causing an insert operation?
Select only the columns needed.

Dependency Injection

admin — Sun, 02 May 2010 09:49:07 +0000

The dependency injection is a hype in the unit tests world. Some hate it, some love it. The dependency injection is injecting the dependency in a system where the objects are disconnected with loose coupling and require dependency injection to make the system to work. For example, a data retrieval manager can have a data connection object. Before the data retrieval is created, the connection object is created in it’s constructor. This dependency can be broken, and the connection object can be passed as a dependency. That’s what dependency inject is. Now both the connection and manager can be tested separately. There are few ways this injection can be done – constructor injection, setter injection. The third type of injection is through service locater. The service located is a container that creates the objects. This takes the responsibility out of the client to create the objects.

There are few things that are bad about DI. Too much decoupling is bad. The client has to create all the objects for a simple thing to work. The overhead of service locater using the reflector can’t give you an idea of how much time some methods to execute in reality.