Hello guys. I am getting an error like this when connecting to database in visual studio 2022.
Prior to this VS 2022 Note you see that VS 2022 has x64 processes. Even if it seems that it warns about Access Database, it is not only about Access Db.
Developers can prefer to use historical OLE Db Providers to connect to SQL Databases. Specially when they want / need to use DataSet / DataTable etc. components.
Almost all x86 Processes (means project references, specially old ones) should be compatible with this situation when these want to use in Project.
Please Check that your reference dlls are x64 or not.
Related
I have inherited a C# code base that started life in VS2013. We are now moving to VS2017 (from VS2015). The solution contains a number of .rptproj projects used to manage the database schemas. After installing MS Report Projects for VS I can now open the .rptproj projects in VS. However, if I create a new database project the file suffix is .sqlproj. As far as I can see these projects are the same, as they appear in the IDE at least, so I'm a little confused as to what the difference is? Is it purely a name change for some reason is is there more significance to this? I'm definitely missing something here.
.sqlproj files are for writing and deploying sql database objects (tables, views, stored procedures etc)
.rptproj files are for writing reporting services reports
They are different and both awesome :)
I have downloaded BIDS and SSDT for 2015, but these don't seem to allow me to open a .rptproj file in my sln. It tells me that the application is not installed. How can I open this? It opens perfectly fine on vs 2012.
Currently the SQL BI project types (SSAS, SSRS, SSIS) are not supported on Visual Studio "15" Preview releases. The BI projects rely on some things not available yet (for example SSIS requires VSTA) and so support is not yet available in that product. The list of available versions to install is on the SSDT download page and will be updated when future versions are supported.
For now, Visual Studio 2015 is the recommended version to use - it is backwards compatible for all project types through SQL Server 2012-2016, with relational DB projects, SSAS and SSRS supported back through SQL Server 2008.
I am working on developing an asp.net mvc web application , using visual studio 2012 professional. now when I want to update my project, for example by adding new features, I do the following steps:-
I copy the project folder.
past it inside a "versioning" folder.
work on the original project , were I add the new features and code.
now if I want to revert my project back before the new features, I can open the folder inside the "Versioning" folder. and so on...
now my current approach is some how sufficient.. but I am trying to find a more automated approach where I can for example revert certain file let say a certain .cs file to its previous version , or revert back my whole project to certain point.
so can anyone advice how Visual studio 2012 can help me in managing my versioning ?
Thanks in advance for any help.
Regards
You'll want to use a version control system like Team Foundation Server (TFS), Git, Mercurial, Subversion, etc. I personally recommend Git. Many of them have a means of integration with Visual Studio 2012 (for example, see How to Connect Visual Studio 2012 with git (github)?). Version control software supports features such as tracking file changes, creating code branches, merging code from different commits/users back together, etc.
Here's what a very simple workflow might look like with version control (see https://guides.github.com/introduction/flow/ for an example of the GitHub flow):
You're ready to add a new feature/start a new version. For simplicity we'll assume you're working on a single branch (e.g. Git "master" branch).
As you program, you make incremental changes to you source code and commit those changes regularly. Each commit gives you a snapshot of the work you've done and you can go back to any commit at any point and compare the changes between commits. The VCS you choose will influence how you synchronize those changes with a central/remote repository. You can even check revision history and look at previous versions of specific files and your code is typically backed up on another server for you without much additional work.
When you're ready to release, you could tag a specific revision (or merge features branches into master, or ... etc.). Whatever the case, you can keep track of all the cumulative changes you've made for each release and be able to revert back to any point.
There are a few other steps you may consider for versioning such as updating the assembly information. In the AssemblyInfo.cs file there is assembly metadata specifying the assembly version, file version (or informational version, which I prefer). See What is AssemblyInfo.cs used for?. You can configure Visual Studio to auto-increment the version numbers.
Team Foundation Server should be available by default with VS 2012, although I'm vague on the details of setting up a TFS server to host your repositories. Visual Studio added direct support for Git (open source, very popular) starting in VS 2013, however there is an extension available for 2012 (https://visualstudiogallery.msdn.microsoft.com/abafc7d6-dcaa-40f4-8a5e-d6724bdb980c). The extension allows you to perform some of the most used Git functions such as committing, branching, and pushing.
Here are some links to get you started:
Why should I use version control?
Using Git with Visual Studio
https://git-scm.com/download/win
https://tortoisegit.org/
https://www.visualstudio.com/en-us/products/tfs-overview-vs.aspx
I use VSTS and it is fantastic. You can use GIT or TFS version control. Both are hosted by Microsoft. I prefer Microsoft due to the idea of long term support and reliability. You can see they are supporting VS 2008 to current.
https://www.visualstudio.com/team-services/pricing/
It is also free for up to 5 users.
From the link posted below.
It has full support for many versions of Visual Studio
Q: Which versions of Visual Studio can I use with Visual Studio Team Services?
A: You can use:
Visual Studio "15"
Visual Studio 2015
Visual Studio 2013
Visual Studio 2012
Visual Studio 2010, requires Service Pack 1 and KB2662296
Visual Studio 2008 SP1, requires GDR update To connect to Team
Services with
Visual Studio 2008 through 2012
Start Visual Studio.
From the Team menu or Team Explorer, go to Connect to Team Foundation Server > Select Team Projects > Servers.
Add your Team Services account ({youraccount}.visualstudio.com).
Select your team project, and finish connecting.
If you get connection errors, try choosing HTTPS as your protocol.
https://www.visualstudio.com/en-us/docs/setup-admin/team-services/connect-to-visual-studio-team-services
GIT Vs TFS Version Control - https://www.visualstudio.com/en-us/docs/tfvc/comparison-git-tfvc
One thing to look into is how you visualize editing and checking in code. I personally find that TFS version control follows a very simple and linear model. I prefer it to git. But its really Apples vs Oranges and usually people like what they are used to. I will say that Git currently is in active development and is not as feature rich as TFS-VC. Not to mention VSTS hooks into their entire ecosystem of plugins, build systems, test infrastructure and all of their cloud platform "Azure"
If you dont need to be sharing your version controlled stuff, I like TurtleSVN. Its simple and I like the UI it has for displaying modifications between versions. It adds a choice on the right-click menu of any file or folder in windows explorer for "TurtleSVN" and then all of the operations can be handled from there.
My Suggestion is still using TFS - I my project which is a product ( ASP.MVC application ) - we are using following structure in TFS..
we have a main branch - DEV branch a QA branch and a SP branch. See screen shot attached)
Main Branch - Where all the code is merged using scripts - before we start with new version of development and then a new DEV branch with version is created from this main branch.. - so we have track of every version and new features added to each version... and For new client the code from Main branch is given.
Dev - Based on features added we create different folder for each new set of features / enhancements and put the version.
SP - After development is completed - the DEV branch is freeze and we create a new branch id SP and deploy the code for QA team - any defect founs are fixed in SP and deployed to QA - once testing is done the code is SP is freeze with QA approved and deployed to main and provided to Clients..
Finally using script - every thing from SP is merged in to Main.. and for new development - a new Branch in DEV is created from the Main..
This way we have track of enhancements / feature for each DEV phase and related SP is available and our product is getting developed in Main.
Hope this Helps..
I have a project created on my own pc with Visual Studio 2012, initialy with Entity Framework 4.5
I made it compatible with Entity Framework 3.5 because the computers where the application will run are Vista ones.. ( O_o )
After lot of debug, creating a new db compatible, creating the model of the new database, I finally performed this first downgrade and it's working on my computer with Entity Framework 3.5 as we can see in this screenshot: http://imagik.fr/view/128976
I can start the .exe on my computer without any problem. I have modified the App.Config connection string to give the right path for the database on their computer and then have tried, just insta crash when it works on mine..
Finally I have installed vs 2008 on one vista computer and I can't import my vs 2012 project, too recent. If I create a new project on 2008 and just create the classes with copy/paste, add libraries and references, I have a problem with my DB. the database.mdf version is 706 and can't be upper than 655.
I'm completely lost with these compatibilities problems... I know we can upgrate a 2008 project to 2012, but is it possible in the other way? Should it be a solution?
If not, what am I supposed to do? They told me "free technology", finally it isn't free at all.....
If anyone already met those kind of problems..
Thanks in advance for your help.
ps: If you need other informations, I can give screens, just ask me.
ps°2: I know there is a lot of problems like mine on the web and on StackOverflow, but I have already done what they said (Edit the properties of the project and make its EntityFramework to 3.5, adding the .csproj of the 2012 on a blank vs 2008 project, etc.)
I downloaded the team explorer 2005 and when I tried to open the application from source control , I am getting the error .csproj applicaion type is not installed.
How can I resolve this ?
In order to open a .csproj you will need to install a version of Visual Studio that supports .csproj`s. There are free versions, called express SKU's, of Visual Studio that should help you out here. It, and the other express SKU's, are available at the following link
http://www.microsoft.com/express/Windows/
You need a CAL (Client Access License) to run just team explorer and access the TFS functionality to check in and check out and other things. If you're wanting to open the projects and make changes you'll need a license for visual studio. There are many different options there. I don't believe you can use the free one in your situation. Using VS professional you'll still need to get the CAL as well to access TFS but if you get one of the team editions of VS you will have the TFS CAL included.
That's how I understand the licensing for TFS/VS but I'm not an expert and it would probably be best to ask your supplier or microsoft about licensing.
I believe Team Explorer allows one to interface with TFS which includes accessing project documentation, filing bugs, and possibly retrieving source code. However, I believe you need Visual Studio to open up project/solution files (i.e. a developer task).
This might be different with Visual Studio 2010 but that's the sales pitch we heard regarding 2008.
In summary, although you need the specific module that loads C# projects. When you installed Team Explorer, although you have the basic IDE, that module is not loaded (is similar to when you install SQL Server client - you have the Visual Studio IDE, but the only module loaded is the SQL Server management Studio). As some of the other guys suggested, try to install Visual Studio C# Express (you can find more information here - http://www.microsoft.com/express/Windows/ - click on Microsoft® Visual C#® 2008 Express Edition). Notice that later on if you want to use web application, you will need to install the web edition and so forth.
When you install Visual Studio Professional (or Team Suite) most of those modules are installed by default.
I hope this info helps.