I have a Visual Studio 2010 database project for my SQL Server 2005 database.
It works fine and has intellisense when editing definition files for objects, but if I want to try running anything against the database as soon as the script file is connected I loose intellisense. I realise this is because Visual Studio is trying to use connection intellisense rather than from the schema of the project.
Is there anyway to force visual studio to always use the schmea of the project so that I can have intellisense all of the time?
Any solutions I have seen so far for this have required the use of a third party product to enable intellisense on SQL Server 2005, which is not an option for me.
Well it looks like this can't be done.
Related
I was using reportviewer 2010 control in visual studio 2010 but i need to start using reportviewer 2012. How can I use the new ASP.NET webforms ReportViewer 2012 control in Visual Studio 2010 (without moving up to visual studio 2012)? Eventually I want to move up to Visual Studio 2012 and dotnet 4.5 but I'd prefer to keep using dotnet 4.0 and Visual Studio 2010 for a little while longer.
I think you are asking how you can 'create reports' for SSRS by the sounds of it, not just display them. Okay so this will sound weird but you need SQL Server 2012 either Enterprise, Developer, Standard with Advanced Tools edition. Any one of those should suffice to get you the tool you need. If you are looking to 'design' reports the tool is an add on to Visual Studio called 'Business Intelligence Development Studio', BIDS for short. For some reason it shows up now as 'SQL Server Data Tools' under 'All Programs' on Windows. You can thank Microsoft for making this version as confusing as possible to people looking to get into SSRS.
To install it you simply install all of SQL Server and when you get to the 'Features' section ensure that BIDS is selected. The version of BIDS IS NOT ON VS 2012, it is on VS 2010. For some reason the SQL team did not make the deployment of SQL Server coincide with Visual Studio so it goes along with VS 2010, NOT 2012. A great many people get this confused but I can say for a fact SSRS is an extension of BIDS, which in turn is an extension of Visual Studio. Not the other way around. You can create localized reports in VS 2012 that are 'rdlc' files but not the full blown SSRS you deploy to a server there.
Ive been working on some stuff with Visual Studio 2008, and SQL 2008 aswell..
Then i opened the project on another computer with 2012 version.
And now when im trying to work with the files in 2008 again, i cant open my database.mdf, becouse the 2012 sql has upgraded my database file...
Anything i can do to save it?
(Btw. the data aint that important, but more the whole table setup and relations)
Install 2012 SQL Server Express with Management tools, attach the MDF and extract the schema by generating "create" scripts for the objects you want using the wizard, then re-run the scripts on the new 2008 DB, don't think there's a way to downgrade. See here.
Or you can just keep developing on top of SQL2012, shouldn't be a problem even if you use visual studio 2008.
I have a clean install of windows 7 with Visual Studio 2010 Premium inc. SP 1. I also just installed the developer edition of SQL Server 2012 .
I now should be able to convert the Visual Studio 2010 database project to an SSDT project. According to this technet blogpost it should be as easy as opening my Visual Studio solution file and follow the conversion wizard. The problem is that the conversion wizard never appears. Also, the "Convert to SQL Server Database project..." context menu item does not exist when right clicking on the VS 2010 database project.
I'm probably missing something in my SQL 2012 installation. The question is: what?
My SQL 2012 install configuration:
In case it helps someone else.
In my case I did not get a wizard of any kind, even though I did ALL necessary installs.
Symptoms:
Open solution in VS2012.
Database project is unloaded, it says it needs migration.
Reload database project, it says it requires functional changes (or something like it). I press OK.
Database project is available, it builds, but when I close VS2012, and re-open the solution, it says the same thing over and over again.
Solution:
Unknown to me VS2012 does create a new project of ssdt type. Unfortunately it doesn't load it. I have a project .dbproj file and a project .sqlproj file. The .dbproj file is loaded.
Remove the database project from the solution.
Add existing project -> select the .sqlproj file. The database project is loaded again. It builds.
Now everything seems well, I can open and build the solution in VS2012 without any problems. Also, I can reopen the solution in VS2010SP1, and it opens and builds without any problems.
Found the problem. Apparently I still needed to download SSDT standalone from http://www.microsoft.com/web/gallery/install.aspx?appid=SSDT. Althought SQL Server Data Tools is listed in the screenshot above.
EDIT: Updated the link. Thanks #ryanwebjackson
If you have a situation where you're trying to migrate from .dbproj created for Visual Studio 2008 to .sqlproj for Visual Studio 2012 you might run into same behavior (no wizzard, can't load project).
In my case there was even quite absurd situation where Visual Studio 2012 created .sqlproj file and copied into it the contents of old Visual Studio 2008 .dbproj.
None of the proposed workarounds helped, I had to first convert from 2008 .dbproj to 2010 .dbproj (using Visual Studio 2010) and then from 2010 .dbproj to .sqlproj (using Visual Studio 2012).
For me something diffrent works.
After migration you will have both *.dbproj and *.sqlproj in project directory.
Just remove project (dbproj and attach existing sqlproj project).
Do not know why solution file is not updated.
I have a visual studio project that was originally built with Visual Studio 2005 Professional. It makes use of some features like crystal reports and building MSI files that are no available in the freely available Visual Studio 2008. I lost my 2005 license so I opted to download the free 2008 edition, and I migrated the project. Predictably, it tells me that certain parts of the project could not be migrated, but it does allow me to work with the other parts (which is totally fine with me). The problem is, because the migration "failed" it wants me to migrate the project every single time I try to open the project.
Can someone show me the break statement for this loop?
Hope this helps Don't sweat migrating legacy .NET projects to Visual Studio 2008
Here is some information to try even doesn't help.
Make sure you open the converted project file.
While writing this question I had a simple idea which fixed the issue. Maybe other people have the same problem or you would like to comment this so I'm posting it anyways.
tldr/simplified question:
How do i use MS SQL Server 2005 Reporting Services in Visual Studio 2010?
Solution:
Just copy the Visual Studio 2008 Reporting DLLs in your project and include them as references. I guess you have to own a licence for vss2008 when doing this but technically this solves the issue.
Original question:
How can i use MS SQL Server 2005 Reporting Services in Visual Studio
2010? The reason i ask this is the following: We migrated to
VSS 2010 as our IDE but are still using MS SQL Server 2005.
Now, i want to change a piece of code in a Project which makes use of
Reporting Services on said SQL Server.
After converting the Solution to a VSS2010 Solution I get BuildErrors
because it can't find the namespaces "ReportViewer" and "Reporting".
That's because the references to
Microsoft.ReportViewer.Common (9.0.0.0)
Micrsofot.ReportViewer.WinForms (9.0.0.0)
Are no longer resolvable. So i have to replace them with the
references to the same Assemblies in Version 10.0.0.0.
After doing that the Solution builds successfully, but when opening
the ReportViewer i get an SoapVersionMismatchException telling me that
for Remote-Processing i have to use Microsoft SQL Server 2008
Reporting Services or higher.
You need to add the old references to your project. You can find them on your 2005 reporting server.
These can be found on your reporting server in the GAC.