原文 VS2012,VS2013,and VS2015Pro+NpgsqlDdexProvider+EFv6 how to(by @kenjiuno)

Reference: #213

Overview

  1. Install Npgsql DDEX (Data Designer Extensibility) provider.
  2. Install Npgsql ADO.NET Data Provider.
  3. Visual Studio’s Entity Data Model wizard will be enabled for PostgreSQL servers.

Prerequisites

Visual Studio 2015 users:

  1. Visual Studio 2015 Professional or greater editions. Express edition won’t work.
  2. Microsoft Visual Studio 2015 Update 1 is available.

Visual Studio 2013 users:

  1. Visual Studio 2013 Professional Update 2 or greater editions. Express edition won’t work.
  2. Microsoft Visual Studio 2013 Update 5 is available.

Visual Studio 2012 users:

  1. Visual Studio 2012 Professional or greater editions. Express edition won’t work.
  2. Visual Studio 2012 Update 5 is available.

PostgreSQL server installed:

  1. Tested on PostgreSQL 9.3.4 (win-x64)

Install DDEX provider (Npgsql 3.0.x)

  1. Grab Setup_NpgsqlDdexProvider.exe from https://github.com/npgsql/npgsql/releases and run it.
  2. Select all components to install.

Note: The version among NpgsqlEntityFramework6.Npgsql and NpgsqlDdexProvider must be same. For example, if you select Npgsql 3.0.5, it needs EntityFramework6.Npgsql 3.0.5. Also NpgsqlDdexProvider 3.0.5.

Install Npgsql ADO.NET Data Provider to Visual Studio (Npgsql 3.0.x)

  1. Launch Visual Studio.
  2. Open [TOOL] menu, and then click [Setup Npgsql DbProviderFactories…]
  3. Click [OK], 2 times.
  4. Restart Visual Studio.

It asks permission to modify your devenv.exe.config:

This process will add the Npgsql in devenv.exe.config:

  <system.data>
<DbProviderFactories>
...
<remove invariant="Npgsql" />
<add name="Npgsql Data Provider" invariant="Npgsql" description=".Net Data Provider for PostgreSQL" type="Npgsql.NpgsqlFactory, Npgsql, Version=3.0.0.0, Culture=neutral, PublicKeyToken=5d8b90d52f46fda7" />
</DbProviderFactories>
</system.data>

Setup succeeded.

Note: It will be prompted if administrative privilege is required to modify your devenv.exe.config.

Prepare new project for testing

  1. Launch Visual Studio.
  2. [FILE]→[New]→[Project…]
  3. [Console Application]
  4. Name is [testef] for example.

Install Npgsql for Entity Framework 6 (3.0.x) from NuGet

  1. Right click project [testef]
  2. [Managet NuGet Packages…]
  3. Type “Npgsql” at [Search Online (Ctrl+E)]
  4. Install “Npgsql for Entity Framework 6” (EntityFramework6.Npgsql). Version is 3.0.5 for now.
  5. EntityFramework 6.0.0 and Npgsql are also installed as part of its dependency.

Notice: The assembly versions of Npgsql and NpgsqlDdexProvider must be same. If, for some reason, you need to install a version which isn’t the latest one from NuGet, you need to use the following command in the NuGet Package Manager Console:

Install-Package EntityFramework6.Npgsql -Version <version> where <version> is the version you want to install. A list of versions available can be found in the NuGet Npgsql page: https://www.nuget.org/packages/Npgsql/

Add Npgsql EFv6 provider

Notice: Recent EntityFramework6.Npgsql NuGet package automatically does this process.

  1. Open [App.config], or [Web.config] for web projects.
  2. Add provider-element into providers-element: <provider invariantName="Npgsql" type="Npgsql.NpgsqlServices, EntityFramework6.Npgsql" />

An App.config having Npgsql EFv6 privoder:

<?xml version="1.0" encoding="utf-8"?>
<configuration>
<configSections>
<!-- For more information on Entity Framework configuration, visit http://go.microsoft.com/fwlink/?LinkID=237468 -->
<section name="entityFramework" type="System.Data.Entity.Internal.ConfigFile.EntityFrameworkSection, EntityFramework, Version=6.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" requirePermission="false" />
</configSections>
<startup>
<supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.5" />
</startup>
<entityFramework>
<defaultConnectionFactory type="System.Data.Entity.Infrastructure.SqlConnectionFactory, EntityFramework" />
<providers>
<provider invariantName="System.Data.SqlClient" type="System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer" />
<provider invariantName="Npgsql" type="Npgsql.NpgsqlServices, EntityFramework6.Npgsql" />
</providers>
</entityFramework>
</configuration>

Add Npgsql ADO.NET Data Provider

You need to declare the Npgsql ADO.NET Data Provider. Edit one of following config files:

  1. App.config or Web.config
  2. machine.config

If you are using NuGet for your application, we recommend to edit: App.config or Web.config

machine.config are placed in these locations. Framework64 will exist on 64-bit Windows:

C:\Windows\Microsoft.NET\Framework\v4.0.30319\Config\machine.config C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Config\machine.config

This is needed part of App.config:

<system.data>
<DbProviderFactories>
<remove invariant="Npgsql"/>
<add name="Npgsql Data Provider"
invariant="Npgsql"
description=".Net Data Provider for PostgreSQL"
type="Npgsql.NpgsqlFactory, Npgsql, Culture=neutral, PublicKeyToken=5d8b90d52f46fda7"
support="FF" />
</DbProviderFactories>
</system.data>

Note: <remove invariant="Npgsql"/> is important, in case of already having <add invariant="Npgsql" ... /> in machine.config.

Edited App.config:

<?xml version="1.0" encoding="utf-8"?>
<configuration>
<configSections>
<!-- For more information on Entity Framework configuration, visit http://go.microsoft.com/fwlink/?LinkID=237468 -->
<section name="entityFramework" type="System.Data.Entity.Internal.ConfigFile.EntityFrameworkSection, EntityFramework, Version=6.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" requirePermission="false" />
</configSections>
<startup>
<supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.5" />
</startup>
<entityFramework>
<defaultConnectionFactory type="System.Data.Entity.Infrastructure.SqlConnectionFactory, EntityFramework" />
<providers>
<provider invariantName="System.Data.SqlClient" type="System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer" />
<provider invariantName="Npgsql" type="Npgsql.NpgsqlServices, EntityFramework6.Npgsql" />
</providers>
</entityFramework>
<system.data>
<DbProviderFactories>
<remove invariant="Npgsql"/>
<add name="Npgsql Data Provider"
invariant="Npgsql"
description=".Net Data Provider for PostgreSQL"
type="Npgsql.NpgsqlFactory, Npgsql, Culture=neutral, PublicKeyToken=5d8b90d52f46fda7"
support="FF" />
</DbProviderFactories>
</system.data>
</configuration>

Build once

  1. Build your project.

New ADO.NET Entity Data Model

  1. Right click project [testef]
  2. [Add]→[New Item…]
  3. [ADO.NET Entity Data Model]
  4. Default name [Model1] for example.
  5. Click [Add]
  6. [EF Designer from database] at Choose Model Contents.
  7. [New Connection] at Choose Your Data Connection.
  8. [PostgreSQL Database] at Change Data Source.
  9. Fill properties in Connection Properties. It is easy to fill everything by setting [ConnectionString].

My sample ConnectionString:

Host=127.0.0.1;Port=5432;Database=npgsql_tests;Username=npgsql_tests;Password=npgsql_tests

Note: PreloadReader and Compatible properies are obsoleted since Npgsql 3.0.0. Please remove them before submitting ConnectionString.

  1. Select [Yes, include the sensitive data in the connection string.] in this case for easy setup.

  2. Select tables which you want, at Choose Your Database Objects and Settings.

Note: remember the text npgsql_tests_efModel at [Model Namespace].

  1. Click OK for Security Warning. T4 Templates generator warns you as it contains just runnable C# code.

  2. You will get a generated model.

Edit your program.cs

Just my sample code for npgsql_tests_ef database.

About the name of “npgsql_tests_efEntities” class, check your [Model Namespace] entered above. Replace “Model” with “Entities”, like it is “npgsql_tests_efModel”.

using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using System.Threading.Tasks; namespace testef
{
class Program
{
static void Main(string[] args)
{
using (npgsql_tests_efEntities Context = new npgsql_tests_efEntities())
{
foreach (Blogs blog in Context.Blogs)
{
Console.WriteLine(blog.BlogId + " " + blog.Name);
}
}
}
}
}

Sample output:

How to check if Npgsql DDEX is working correctly. (Npgsql 3.0.x)

(by @kenjiuno)

Reference: #718

NpgsqlDdexProvider 3.0.4 and later has a feature to check Npgsql installation status of your .NET project.

  1. Right click your .NET project
  2. Click [Check Npgsql project installation]

Click a button to start the check!

It will suggest them if you need one or more actions:

[Test and result] shows test cases and their results:

How to check if Npgsql DDEX was correctly loaded. (Npgsql 2.x)

(by @kenjiuno)

Reference: #67

Here are tips to check.

  • Check your connection dialog:

  • Make sure to edit both x86 and x64’s machine.config. VS2013 runs 64bit mode on x64 machine. C:\Windows\Microsoft.NET\Framework\v4.0.30319\Config\machine.config C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Config\machine.config

<system.data>
<DbProviderFactories>
<add name="Npgsql Data Provider"
invariant="Npgsql"
description=".Net Data Provider for PostgreSQL"
type="Npgsql.NpgsqlFactory, Npgsql, Version=2.0.12.91, Culture=neutral, PublicKeyToken=5d8b90d52f46fda7"
support="FF" />
</DbProviderFactories>
</system.data>

Note that the Version attribute above should match the version of the Npgsql Assembly you are using.

NpgsqlDdexProvider build tips

(by @kenjiuno)

Reference: #213

VS2010 users

You’ll need VS2010 Professional or greater.

SP0 users:

SP1 users:

If you need newer NpgsqlDdexProvider2010.pkgdef, create your own manually. pkgdef is a kind of registry file for our DDEX registration. Note: It is needed only if you change contents of NpgsqlDataProviderRegistration class.

Command example:

H:\Dev\Npgsql\NpgsqlDdexProvider>"H:\Program Files (x86)\Microsoft Visual Studio 2010 SDK SP1\VisualStudioIntegration\Tools\Bin\CreatePkgDef.exe" /out=NpgsqlDdexProvider2010.pkgdef /codebase bin\Release-net40\NpgsqlDdexProvider.dll

Output:

	Visual Studio (R) PkgDef Creation Utility.
Copyright (c) Microsoft Corporation. All rights reserved. CreatePkgDef : warning : The Assembly specified at 'bin\Release-net40\NpgsqlDdexProvider.dll' cannot be loaded because an alternate copy with the same identity
exists in the Assembly probing path at 'H:\Dev\Npgsql\NpgsqlDdexProvider\bin\Release-net40\NpgsqlDdexProvider.dll'. The Assembly at 'H:\Dev\Npgsql\NpgsqlDdexPro
vider\bin\Release-net40\NpgsqlDdexProvider.dll' will be loaded instead.
Assembly: NpgsqlDdexProvider 1.0.0.0
Output file: NpgsqlDdexProvider2010.pkgdef インストールされている製品: NpgsqlDdexProviderPackage、Version 1.0
パッケージ: NpgsqlDdexProviderPackage {958b9481-2712-4670-9a62-8fe65e5beea7}
サービス: PostgreSQL Provider Object Factory SUCCEEDED: NpgsqlDdexProvider

Check: How to create a pkgdef file for your Visual Studio Packagehttp://blogs.msdn.com/b/dsvst/archive/2010/03/08/how-to-create-a-pkgdef-file-for-your-visual-studio-package.aspx

VS2012 users

You’ll need VS2012 Professional or greater.

VS2013 users

You’ll need VS2013 Professional or greater.

VS2015 users

You’ll need VS2015 Professional or greater.

How to debug Npgsql DDEX extension

In order to debug it, you will need to use the Experimental Instance of Visual Studio.

  • In the NpgsqlDdex project, right click and select properties.
  • Go to Debug tab
  • Click on the radio button for Start External Program. Point it to the devenv.exe binary. On my machine it’s located at

C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\devenv.exe

Then set the command line arguments to /rootsuffix Exp

Save everything and now, just right click the NpgsqlDdex project -> Debug -> Run in a new instance. A new Visual Studio instance should be run where the extension will be made available and you can debug it in the first visual studio instance.

Reference: http://stackoverflow.com/questions/9281662/how-to-debug-visual-studio-extensions

Visual Studio Support (DDEX)的更多相关文章

  1. Oleg Sych - » Pros and Cons of T4 in Visual Studio 2008

    Oleg Sych - » Pros and Cons of T4 in Visual Studio 2008 Pros and Cons of T4 in Visual Studio 2008 Po ...

  2. Pros and Cons of T4 in Visual Studio 2008

    Oleg Sych - » Pros and Cons of T4 in Visual Studio 2008 Pros and Cons of T4 in Visual Studio 2008 Po ...

  3. VS 远程调试之 “The visual studio remote debugger does not support this edition of windows”

    The error message "The visual studio remote debugger does not support this edition of windows&q ...

  4. News: Visual Studio Code support debugging Linux Apps

    http://arstechnica.com/information-technology/2015/11/visual-studio-now-supports-debugging-linux-app ...

  5. CMake support in Visual Studio

    Visual Studio 2017 introduces built-in support for handling CMake projects. This makes it a lot simp ...

  6. HTML5 Support In Visual Studio 2010

    最近HTML5浪潮已经开始了,VS2010已经有一个扩展支持在HTML5智能提示.你可以从这里下载这个扩展: http://visualstudiogallery.msdn.microsoft.com ...

  7. Create an offline installation of Visual Studio 2017 RC

    Create an offline installation of Visual Studio 2017 RC ‎2016‎年‎12‎月‎7‎日                             ...

  8. 安装MySql for Visual Studio的坑

    阅读目录 问题描述 解决过程 解决方案 总结 回到顶部 问题描述 安装MySql for Visual Studio 一般来说是为了能在VS的服务器数据连接的数据源中能选择MySql类型,如下图: 但 ...

  9. 【转载】保哥 釐清 CLR、.NET、C#、Visual Studio、ASP.NET 各版本之間的關係

    我常常不仅仅逛 博客园,还会去找国外,特别是台湾的技术部落格,发现好的文章,我便会收录,今天我转载或者全文复制,在Google 博客园,一位叫保哥, 釐清 CLR..NET.C#.Visual Stu ...

随机推荐

  1. HTML5特性:使用async属性异步加载执行JavaScript

    HTML5让我兴奋的一个最大的原因是,它里面实现的新功能和新特征都是我们长久以来一直期待的.比如,我以前一直在使用placeholders,但以前必须要用JavaScript实现.而HTML5里给Ja ...

  2. Win10环境下的Scrapy结合Tor进行匿名爬取

    本文内容来源:http://blog.privatenode.in/torifying-scrapy-project-on-ubuntu/ 在使用Scrapy的时候,一旦进行高频率的爬取就容易被封IP ...

  3. gcc链接程序时出现undefined reference to""错误

    如:: undefined reference to ‘mq_unlink',意思是指函数mq_unlink没有定义. 可以使用如下步骤找到该函数所在的库: 1).查找哪些库包含了或使用了该函数:gr ...

  4. javascript 柯里化

    先看一下代码 function add(){ var sum=0; for(var i=0;i<arguments.length;i++){ sum+=arguments[i]; } retur ...

  5. Microsoft Azure 全球状态

    除了mooncake的中国大陆区域 Azure status http://azure.microsoft.com/en-us/status/?rnd=1#current http://azure.m ...

  6. android连接本地tomcat服务器,报timeout

    1.在eclipse环境下连接时,没有任何问题 2.直接将服务端发布到tomcat服务下,报timeout 3.查明原因: 3.1打开IE访问,一切正常,可以获取到数据,说明不是服务端的问题 3.2打 ...

  7. 2016 系统设计第一期 (档案一)MVC bootstrap model弹出子页面

    通过bootstrap  弹出modal-dialog 子页面 ,例如我要弹出子页面:areaitem_sub_One.html. 具体步骤如下: 第一步:新建 areaitem_sub_One.ht ...

  8. 音频播放、录音、视频播放、拍照、视频录制-b

    随着移动互联网的发展,如今的手机早已不是打电话.发短信那么简单了,播放音乐.视频.录音.拍照等都是很常用的功能.在iOS中对于多媒体的支持是非常强大的,无论是音视频播放.录制,还是对麦克风.摄像头的操 ...

  9. BitmapSource ConvertTo Bitmap

    偶遇需要把 BitmapSource 转成 Bitmap. .. using System; using System.Drawing; using System.Drawing.Imaging; u ...

  10. C# File

    http://msdn.microsoft.com/zh-cn/library/system.io.file(v=vs.110).aspx using System; using System.IO; ...