Daily Archives: February 11, 2010

Vermont IT Jobs: .NET Developer in MIddlebury

Jobs

I worked with the small development team at this company a few years ago as a mentor and it is a great work environment. Super nice folks. Company has a deep Vermont history and you get to be in Middlebury.

Co-Operative Insurance (http://www.co-opinsurance.com/)

We are currently seeking a new addition to our .NET development team. Applicants should have a strong technical background as well as excellent communication and interpersonal skills. Additionally, applicants should possess the ability to creatively solve problems in a sound, efficient manner. As a member of our .NET team, you will be expected to write neat, efficient code containing in-line documentation. Furthermore, developers are expected to fully test and document their work for the end user.

Qualified candidates must have experience with the following technologies: VB.Net, Visual Studio, SQL, ASP.NET, HTML/XHTML/DHTML/JavaScript/AJAX and Source Control Software. Experience with the following would be a plus: Java, XSL, Subversion, and Cruise Control.

This full-time position comes with a great benefits package, a friendly, professional work environment, and an emphasis on personal-professional life balance. Our high retention levels back up those claims. Based in Middlebury, Co-operative Insurance Companies provides financial security to home, auto, farm and small business owners across VT and NH. Our 70 employees are dedicated to offering top-notch service to our Co-op members.

Interested candidates should send a resume and cover letter (no later than 2/26/2010) as follows:

jobs@ciui.net

or

Human Resources

Co-operative Insurance Companies

PO Box 5890

Middlebury, VT 05753

Beware Self-Tracking Entities Conflict with Entity Framework CTP & VS2010 RC

Data Access

Adding a note to highlight Damien’s comment below. Damien is on the EF team and does not recommend using the current Feature CTP with the RC. A new version will be available "soon".

In comments of another blog post Ivan reminds me of something else I ran into the the VS2010 RC.

I tweeted on Tuesday that the Self-Tracking Entities template is now “in the box”.

I also blogged on Tuesday about a change to a file, EF.Utility.CS.ttinclude (or EF.Utility.VB.ttinclude) which the EF T4 Templates depends. The RC version is different from the Beta 2 version.. Using the Beta 2 EF POCO Template with VS2010 RC

The EF Feature CTP contains Code Only functionality and an earlier version of the STE template. Like the POCO template, that STE template depends on the Beta 2  version of the ttinclude file. But the STE template in the VS2010 RC depends on the newer version of the ttinclude file.

If you install the EF Feature CTP on top of the VS2010 RC, you will overwrite the Self Tracking Entities template with the old version and it will no longer work.

I tried to outsmart the process by saving the Item Template zip files, installing the CTP and then copy the RC zip files over the ones which  the CTP installed. That didn’t work out very well.

Option 1

However, doing a repair on VS2010 RC after installing the Feature CTP (and in my case totally mucking things up trying to be clever with the zip files) let me have my cake (Code Only support that works with the VS2010 RC -yay) with the icing (the RC version of teh Self-Tracking Entities which got reinstalled during the repair).

Option 2

Another alternative is to run the STE template item before installing the CTP. The STE template item creates two template files, one for the context and the other for the entities. Only the entities template is impacted by the Feature CTP installation. Copy the contents of the entities template file somewhere. Then after installing the CTP, you’ll initially create the Beta 2 version of the entities template file, just copy the code from the new file into the template file that’s created.

Option 3
If you don’t need to use Code Only, don’t install the Feature CTP! 🙂 Originally, the Feature CTP was a source for Code Only support, STEs and the POCO template. The POCO template is now an extension (although see the above link for some current incompatibility issues with the RC) and STEs are now in the box.

Eventually these conflicts will all get sorted out.