- GIT to SVN Quick Start May 23, 2013
- Entity Framework 4 (EF4) with Visual Studio 2010 and Pluralisation January 30, 2011
- Error: IIS SSL certificate re-issue and the issuer of the certificate not being trusted with the error : “The issuer of this certificate could not be found” October 10, 2010
- Code-First Development with Entity Framework 4 July 18, 2010
- Protected: Bikes and Video April 25, 2010
- Visual Studio 2010 and .NET 4 officially released today April 13, 2010
- Protected: Visual Studio 2010 Pending Release April 7, 2010
- .NET web.config WCF Settings February 19, 2010
- OziExplorer Tracklog File Format February 16, 2010
- Baited Remote Underwater Video Stations February 6, 2010
- Ten things to do with your new friend PALRO February 5, 2010
- Specifying/changing the database when using Web Parts in an ASP.NET application February 3, 2010
- God mode on Windows 7 January 11, 2010
- Protected: Windows Registry interaction with 64 and 32 bit applications January 7, 2010
- Retrieving COM class factory failed due to the following error: 80040154 January 7, 2010
- Integrated security with IIS and .NET January 7, 2010
- IIS Hosted WCF Service Fails January 5, 2010
- Getting IIS Debugging and WCF working under Vista and Windows 7 with VS2008 January 5, 2010
- WinForms applications – No Touch Deployment (NTD) and gotchas January 5, 2010
- First post January 5, 2010
Category Archives: Development
Tips for using GIT with Visual Studio 2012 and an SVN server repository.
Tools for VS2012: Getting started with git in Visual Studio 2012
Using GIT Bash from context menu:
Clone repo from SVN
git svn clone -s https://url
With the recent release of Microsoft’s EF4 with Visual Studio there is some debate around the use of pluralisation of table names.
Standard database theory is taught to use singular entity names, i.e. Genre and the table names should match this singular naming convention, i.e. Genre not Genres.
With EF4, whether using the Code First (CF) features or not, the table names are expected to be pluralised. This is an issue if you prefer to stick with the singularised table names or don’t have a choice on pre-existing databases. It is difficult to change an existing database, especially if that database is being used by other programs or reports within an organisation. This also causes some conflicts when an entity such as Person is used – the EF pluralises this as Persons but perhaps People would be a better option.
This post shows how to get around the EF pluralisation for whatever reason you need. Continue reading
The EF Code-First Library is a very cool feature of the Visual Studio 2010 tools that will allow developers to get their applications running quickly – a full persistent data entity model can be created without having to configure a database, run any tools, configure any XML files, or define any base data entity classes. One of the coolest things is the way the database model can be changed automatically when changes to the entity model are made and the automatic creation of the primary keys and relationships between the tables. This should be a real time saver to developers.
Visual Studio 2010 and .NET 4 officially released today. http://weblogs.asp.net/scottgu/archive/2010/04/12/visual-studio-2010-and-net-4-released.aspx Enjoy!
There is no excerpt because this is a protected post.
I love the way the .NET web.config file allows the appSettings and connectionStrings sections to reference another file. It provides easy support for differing deployment environments as the settings for each environment are kept in their own files and can … Continue reading
When using Web Parts in an ASP.NET application, if personalization is enabled (which is the best reason for using Web Parts), the personalization is stored in a SQL database.
This article details the steps to set this up or to change the default location. The default is the sql express instance on a development machine – my preference is for the SQL 2008 database on my network, but you will also need to specify the database to use when deploying your application.
The database used by the WebPart, or more precisely the WebPartManager, is the same one used by the membership and role providers. To create the database on either SQL2005 or SQL2008, run aspnet_regsql from the C:WindowsMicrosoft.NETFrameworkv2.0.50727 folder. This will run a wizard allowing you to specify where you would like the database created – you will need an instance of SQL Server 2005 or 2008 installed before doing this.
There is no excerpt because this is a protected post.
When installing a new version of Windows 7 (64 bit), I came across this error when attempting to run one of my web services:
Retrieving COM class factory failed due to the following error: 80040154
No real explaination on what component was causing the problem, but stepping into the code, there is a dependency on a third party COM DLL to communicate with a remote server. The COM component is 32 bit – getting it to run in the 64 bit environment is the issue.
Setting up a new Windows 7 machine had me challenged remembering all of the things that need to be done to get my .NET applications all working again, especially ones that use any kind of integrated windows security with IIS, and connect to a database and web services.
The main one that gets me thinking everytime is the impersonation account if a Windows’ account is setup to connect to a database. This would typical be needed when connecting to a web service that connects to a database. One way to achieve this is to use SQL security to maintain the account and store the user/password in the web.config but this has some security concerns in that the password is stored in clear text. This also requires the password to maintained in multiple places, which is not desirable.
When attempting to get a new machine running, I have come across an issue getting IIS hosted WCF services to instantiate.
The error is typically something like the following:
Unhandled Exception: System.ServiceModel.ProtocolException: The remote server returned an unexpected response: (405) Method not allowed.
This can occur if ASP.NET isn’t installed or the .svc file is not mapped to the aspnet_isapi.dll
After installing VS2008 on Vista and attempting to fire up a WCF application built with a .NET framework I built a couple of years ago now, I found the WCF channel was failing with no hint as to the problem. This issue also applies for running on Windows 7.
The framework architecture hosts the WCF service in IIS. When opening the solution with VS2008, I was presented with the need to run VS as an administrator. That problem is sorted easily enough, but is a bit intrusive.
Often when .NET WinForms applications are created, developers do not consider the various deployment options available and panic when it comes time for deployment and default to using ClickOnce. This is not a good strategy as the architecture of the application is not well considered with this in mind and limits the deployment options.