blocks|key|361313|text|我的猜测是，使用VWD，您的解决方案更有可能部署到第三方服务器，其中许多服务器不允许动态附加SQL+Server数据库文件。从而允许另一种连接类型。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|361314|IDE行为的这种差异是升级到完整版的主要原因之一。|361315|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

My guess is that with VWD your solutions are more likely to be deployed to third party servers, many of which do not allow for a dynamically attached SQL Server database file. Thus the allowing of the other connection type.

This difference in IDE behavior is one of the key reasons for upgrading to a full version.

blocks|key|360613|text|您应该能够选择“SQL+Server数据库文件”选项来获取正确类型的数据库(+system.data.SqlClient提供程序)，然后手动更正连接字符串以指向您的数据库。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|360614|我认为这些数据库选择背后的原因可能是这样的：|360615|360616|如果您使用的是速成版，而不是Visual+Web+Developer，那么您可能正在构建一个桌面程序。|unordered-list-item|360617|如果您正在构建一个桌面程序，并且您正在使用速成版，那么您可能是一个业余爱好者或uISV-er，在家里工作，而不是为公司做开发。|360618|如果你不是为公司进行开发，你的应用程序可能是为最终用户设计的，你的数据存储可能是在他们的本地机器上进行的。|360619|你真的不应该把服务器级的数据库部署到最终用户的桌面上。进程内数据库(如Sql+Server+Compact或MS+Access+)更为合适。|360620|360621|然而，这种逻辑并不完全成立。即使这4点中的每一点在90%25的情况下都是正确的，但当你应用这四点时，它只适用于~65%25的受众，这意味着高达35%25的快递市场可能会合法地想要与服务器级数据库交谈，这是一个重要的群体。因此，简化(贪婪)版本：|360622|360623|一个真正的数据库服务器(以及运行它的硬件)需要真正的金钱。如果你能使用它，你至少应该能买得起visual+studio的标准版。|360624|360625|entityMap^0|13|L|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@$9|11|A|12|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|13|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|14|8|@]|D|@]|E|$]]|$1|I|3|J|5|K|7|15|8|@]|D|@]|E|$]]|$1|L|3|M|5|K|7|16|8|@]|D|@]|E|$]]|$1|N|3|O|5|K|7|17|8|@]|D|@]|E|$]]|$1|P|3|Q|5|K|7|18|8|@]|D|@]|E|$]]|$1|R|3|-4|5|6|7|19|8|@]|D|@]|E|$]]|$1|S|3|T|5|6|7|1A|8|@]|D|@]|E|$]]|$1|U|3|-4|5|6|7|1B|8|@]|D|@]|E|$]]|$1|V|3|W|5|K|7|1C|8|@]|D|@]|E|$]]|$1|X|3|-4|5|6|7|1D|8|@]|D|@]|E|$]]|$1|Y|3|-4|5|6|7|1E|8|@]|D|@]|E|$]]]|Z|$]]

You should be able to choose the SQL Server Database file option to get the right kind of database (the <code>system.data.SqlClient</code> provider), and then manually correct the connection string to point to your db.

I think the reasoning behind those db choices probably goes something like this: 

<ul>
<li>If you're using the Express Edition, and you're not using Visual Web Developer, you're probably building a desktop program.</li>
<li>If you're building a desktop program, and you're using the express edition, you're probably a hobbyist or uISV-er working at home rather than doing development for a corporation. </li>
<li>If you're not developing for a corporation, your app is probably destined for the end-user and your data store is probably going on their local machine.</li>
<li>You really shouldn't be deploying server-class databases to end-user desktops. An in-process db like Sql Server Compact or MS Access is much more appropriate.</li>
</ul>

However, this logic doesn't quite hold. Even if each of those 4 points is true 90% of the time, by the time you apply all four of them it only applies to ~65% of your audience, which means up to 35% of the express market might legitimately want to talk to a server-class db, and that's a significant group. And so, the simplified (greedy) version:

<ul>
<li>A real db server (and the hardware to run it) costs real money. If you have access to that, you ought to be able to afford at least the standard edition of visual studio.</li>
</ul>

blocks|key|3150197|text|如果您正在使用它来获取LINQ+to+SQL，1)获取免费的Visual+WEB+Developer，使用它连接到SQL+Server实例，创建您的LINQ接口，然后将生成的文件复制到您的Vis-Dev项目中(我不使用VD，因为它听起来很有趣)。仅包含*.dbml文件。Vis-Dev环境需要一两秒钟的时间来识别支持文件。这是一个小小的额外步骤，但肯定比手工完成要好，或者完全放弃，甚至更糟，为此买单。哇哈哈哈哈。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3150198|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

If you are using this to get a LINQ to SQL which I do and wanted for my Visual Developer, 1) get the free Visual WEB Developer, use that to connect to SQL Server instance, create your LINQ interface, then copy the generated files into your Vis-Dev project (I don't use VD because it sounds funny). Include only the *.dbml files. The Vis-Dev environment will take a second or two to recognize the supporting files. It is a little extra step but for sure better than doing it by hand or giving up on it altogether or EVEN WORSE, paying for it. Mooo ha ha haha.

blocks|key|3150216|text|我能让C#+Express2008正常工作的唯一方法就是移动数据库文件。因此，我打开SQL+Server+Management+Studio，删除数据库后，将文件复制到我的项目文件夹中。然后，我将数据库重新连接到management+studio。现在，当我尝试附加到本地副本时，它起作用了。显然，您不能多次使用同一个数据库文件。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3150217|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

The only way I was able to get C# Express 2008 to work was to move the database file. So, I opened up SQL Server Management Studio and after dropping the database, I copied the file to my project folder. Then I reattached the database to management studio. Now, when I try to attach to the local copy it works. Apparently, you can not use the same database file more than once.

blocks|key|363994|text|解决方法：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|363995|363996|在Visual+Web+Developer速成版中打开解决方案。它不会加载解决方案中的某些项目，但这是正常的。|ordered-list-item|363997|在数据库资源管理器中从SQL+Server建立到所需数据库的新连接。|363998|添加一个新的类库项目。|363999|添加一个LINQ+Classes项目并将其链接到database.|364000|Close+solution.|364001|Open+|364002|+solution+in++C#+Express.|364003|现在，您就拥有了一个链接到Visual+C#+Express中的SQL+Server数据库的LINQ+to+SQL类库。|364004|更新|offset|length|style|BOLD|364005|该解决方案适用于Visual+Studio+Express+2010。|364006|entityMap^0|0|0|0|0|0|0|0|0|0|0|0|2|0|0^^$0|@$1|2|3|4|5|6|7|13|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|14|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|15|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|16|8|@]|9|@]|A|$]]|$1|H|3|I|5|E|7|17|8|@]|9|@]|A|$]]|$1|J|3|K|5|E|7|18|8|@]|9|@]|A|$]]|$1|L|3|M|5|E|7|19|8|@]|9|@]|A|$]]|$1|N|3|O|5|E|7|1A|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|1B|8|@]|9|@]|A|$]]|$1|R|3|S|5|6|7|1C|8|@]|9|@]|A|$]]|$1|T|3|U|5|6|7|1D|8|@$V|1E|W|1F|X|Y]]|9|@]|A|$]]|$1|Z|3|10|5|6|7|1G|8|@]|9|@]|A|$]]|$1|11|3|-4|5|6|7|1H|8|@]|9|@]|A|$]]]|12|$]]

Workaround:

<ol>
<li>Open your solution in Visual Web Developer Express. It will not load some of the projects in the solution but it is ok.</li>
<li>Make a new connection in Database Explorer to the required database from SQL Server.</li>
<li>Add a new class library project.</li>
<li>Add a LINQ to SQL Classes item and link it to your database.</li>
<li>Close the solution.</li>
<li>Open the solution in Visual C# Express.</li>
</ol>

Now you have a LINQ to SQL classes library that is linked to your SQL Server database in Visual C# Express.

Update

The solution is for Visual Studio Express 2010.

blocks|key|3363301|text|为了方便起见，我碰巧在windows窗体中启动了我的家庭业务应用程序。我目前正在使用Visual+C#+Express2010/+SQL+Server2008+R2+Express来开发它。我遇到了与OP相同的问题，我需要连接到SQL+server的一个实例。我在这里跳过细节，但该数据库将是2-3台计算机之间同步的合并数据库，这些计算机也将使用我现在正在开发的应用程序。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3363302|我找到了一个快速的解决方法，至少我想我找到了，因为我现在可以在tableadapter中使用我的存储过程了，到目前为止没有任何问题。|3363303|我在app.config中复制粘贴了一个我在工作中使用的不同项目(+SQL+)的VS2010连接，并在那里更改了我需要的一切。当我返回到我的Settings.settings时，我只需要确认我想要app.config文件中的内容。我能看到的唯一缺点是你不能“测试”连接，因为当你进入连接字符串的配置时，你不能去任何地方，因为"SQL+Server“不是一个选项。另一个缺点是您需要手动输入所有内容，因为您无法使用任何向导来使其工作。|3363304|我不知道我是否应该这样做，但至少我现在可以连接到我的SQL服务器了:)。|3363305|编辑:|offset|length|style|BOLD|3363306|它仅适用于SQL+Server2008SQL+R2+Express实例。如果你尝试使用SQL+Server2008StudioWorkgroup或更高版本，你会收到一个来自Visual+Studio2010Express的令人讨厌的警告，告诉你“你不能在当前版本的C#中使用这个连接”。当我试图修改我的一些表格适配器时，我得到了它。我切换回SQL+Express实例进行开发，它再次正常工作。|3363307|entityMap^0|0|0|0|0|0|3|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|V|8|@$J|W|K|X|L|M]]|9|@]|A|$]]|$1|N|3|O|5|6|7|Y|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|Q|$]]

I just happened to have started my home business application in windows forms for the convenience. I'm currently using Visual C# Express 2010 / SQL Server 2008 R2 Express to develop it. I got the same problem as OP where I need to connect to an instance of SQL server. I'm skipping details here but that database will be a merged database synched between 2-3 computers that will also use the application I'm developing right now.

I found a quick workaround, at least, I think I did because I'm now able to use my stored procedures in tableadapters without any issues so far.

I copy pasted an SQL connection that I used in a different project at work (VS2010 Premium) in the app.config and changed everything I needed there. When I went back to my Settings.settings, I just had to confirm that I wanted what was inside the app.config file. The only downsides I can see is that you can't "test" the connection since when you go inside the configuration of the connection string you can't go anywhere since "SQL Server" is not an option. The other downside is that you need to input everything manually since you can't use any wizards to make it work.

I don't know if I should have done it that way but at least I can connect to my SQL server now :).

EDIT :

It only works with SQL Server 2008 R2 Express instances. If you try with SQL Server 2008 R2 Workgroup and up, you'll get a nasty warning from Visual C# 2010 Express telling you that "you can't use that connection with the current version of Visual Studio". I got that when I was trying to modify some of my tableadapters. I switched back to an SQL Express instance to develop and it's working fine again.

I find it odd that in Visual C# 2008 Express edition, when you use the database explorer, your options are:

<ol>
<li>Microsoft Access</li>
<li>SQL Server Compact 3.5, and </li>
<li>SQL Server Database File. </li>
</ol>

BUT if you use Visual Web Developer 2008 Express, you can connect to a regular SQL Server, Oracle, ODBC, etc.

For people developing command-line or other C# apps that need to talk to a SQL Server database, do you really need to build your LINQ/Data Access code with one IDE (Visual Web Developer) and your program in another (Visual C#)? 

It's not a hard workaround, but it seems weird. If Microsoft wanted to force you to upgrade to Visual Studio to connect to SQL Server, why would they include that feature in one of their free IDEs but not the other? I feel like I might be missing something (like how to do it all in Visual C#).

Connecting to SQL Server with Visual Studio Express Editions

集成开发环境

Visual Studio

数据存储

SQL Server

数据库

服务器

我发现奇怪的是，在Visual C# 2008速成版中，当您使用数据库资源管理器时，您的选项是：Microsoft AccessSQL Server Compact 3.5和SQL Server数据库文件。但如果您使用Visual Web Developer 2008 Express，则可以连接到常规的SQL Serv...

问使用Visual Studio速成版连接到SQL Server
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问使用Visual Studio速成版连接到SQL ServerEN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问使用Visual Studio速成版连接到SQL Server
EN