Visual Studio and databases

/prog/
I have vs professional and sql server 2005, when I want to add a webserver to a project it tells me it can't and that I have to install sql 2005 express, wtf ?

Did you try installing 2005 express?

>>2
I will try this as the last solution, if I can avoid to have two instances of SQL 2005 and work with SQL 2005 developer only via VS it would be cool.

use Emacs

>>4
I've used emacs for years, now I'd like to try something different, thanks.

>>5
Vim (or `ed' if there are too many commands for you).

anyone ?

>>1
>add a webserver to a project

Hahahaha. You are actually using enterprise retard features like that?

Get the fuck out, seriously.

Add a webserver to a project, what the fuck.

add a webserver to a project
Hahaha. Seriosuly, what the fuck?

>>8
I meant a database, you even weren't able to correct it yourself moron

>>10
Adding a database is only slightly less moronic.

I can't remember ever having "added a database" to any project I developed. YOU JUST INCLUDE THE FUCKING DATABASE LIBRARIES AND THEN CONNECT TO IT SOMEWHERE. YOU DON'T "ADD A DATABASE" TO YOUR PROJECT, YOU WIZARD USING PIECE OF SHIT.

I imagine this is one of those horrible contraptions where you "add a database" to your project and then have to specify your queries in some awkward dialog box which is actually 100 times harder to learn than SQL, which will in turn translate your input into a horribly inefficient SQL statement and then generate 50 layers of C++ code, which will likely include at least 3 M$ database access interfaces layered on each other (first of which will probably be an MFC-something, followed by an ActiveX/COM-something, followed by ODBC) and then at the highest level leave you with some funny C++ objects, like in those beginner examples, where you have an object called CEmployees with get and set methods for every column like getSalary() and setSalary(). And when something goes wrong, one of the lower layers will just pop up a useless dialog box saying "lol I think the database doesn't work, error code 3453458934537393", after which your program will just crash and neither your users nor you will have the slightest clue what the fuck just happened because you never bothered to learn SQL or how a database server actually works.

Worse yet, when you look up the error code in MSDN, it will translate into something incredibly useful like "the parameter is invalid". LOL.

tl;dr go die in a fire, enterprise faggot.

http://www.prizerebel.com/index.php?r=51791

>>11
"I can't remember ever having "added a database" to any project I developed"
SO get the fuck out. I ask how to do something, not the advice of a degenerated for who CAPS LOCK IS CRUISE CONTROL FOR COOL. Get a life, thanks.
>>12
tl;dr

>>14
Why not change your project, moron?

>>12
That was one of the best posts I've read today. I applaud you, Anonymous.

>>14
Seriously, wtf. Projects don't have databases, database applications have databases. I've used ODBC wrappers to connect to a MySQL database (in b4 "MySQL fag"). I've never used SQL Express myself, but I'd imagine it runs as a standalone application which you have to configure separately, then connect to. And hell, it probably has an ODBC wrapper, which isn't quite as bad as >>12 makes it out to be.

tl;dr rtfm, fuckhead.

Finally I got it working.
>>16
It's just that I find it stupid to propose to add an mdf file to the project to finally yield "you need SQL 2005 express lol", because you can't customize this option and attach it to another sql server.

some thread for more   details You should   brush up your   sleeve because no   amount of superficial.

^{Back to /b/, ``GNAA Faggot''}

22 Name: Anonymous 2011-01-31 20:33

<-- check em dubz