Maybe it's me, hopefully I am missing something.
I added some Extended Properties to tables and columns in my MSSQL 2008 database. In Visual Studio 2010 I created a new database project, ran a "schema comparison" to load the DB into my project, and it didn't pick up the Extended Properties.
Can anyone comment on what I might have done wrong?
Thanks.
I believe extended properties are ignored by default in schema comparisons. You can include them by opening the "Schema Compare Options" dialog, select the Object Types tab, and ensure the Extended Properties checkbox is checked. Click OK. The comparison should now include extended properties.
You can also change the default settings for subsequently created comparisons by going to Tools -> Options -> Database Tools -> Schema Compare. That'll give you the same dialog as above.
Related
I am currently working on a software written in C++ that consists of 70+ projects in Visual Studio. I would like to increase the compiler level for all those projects without clicking through 70+ project property windows to set the new value for the compiler warning level.
Is there any way to quickly set the compiler warning level for all projects in a Visual Studio solution?
Select all projects, then click on properties. It will open properties page. Here select "All Configurations" and "All Platforms". Then set appropriate warning levels, which will apply to all projects/configurations/platforms.
You may de-select any config/platform, and apply the warning level for all projects. Consider hitting "Configuration Manager..." button on right.
If you are willing to edit the .VCXProj - do that! It will be fastest, but please backup all of them.
Another approach is to have a common header file, and place:
#pragma warning(error:<warning-number>)
This allows you to have more finer control to all warnings. But, you'd need to write almost all of them in header. But, you can configure for different builds.
I am using Visual Studio 2010 Shell and I have had to change my ProtectionLevel to 'DontSaveSensitive' mid project.
Now I get an error: Basic Checks.dtsx has a different ProtectionLevel than the project.
However, there is nowhere in the Project properties that I can see where the ProtectionLevel can be changed to match. All searches seem to indicate this is easy in VS 2012 but can't find any info for VS 2010
Any help would be greatly appreciated!
thanks
Ravi
You have two different places where you can set ProtectionLevel.
First place is properties pane of a package, second place is properties pane of entire project (right click on a project and you will find it under Common Properties). Ensure that you have the same setting in both places.
I'm in the edmx editor of visual studio, and I have a column that I want to map to a new property.
So I right click on my entity -> add -> new scalar property.
And the instead of adding the entity , the IDE goes to the Mapping details windows and select me the Column that isn't mapped.
Did you ever encounter this kind of bug ?
Save your model. Close Visual Studio. Start Visual Studio and open your edmx.
Now it should work (did it for me.)
Consider it a bug in Visual Studio.
I have Visual Studio 2005 Team Edition for DB Professionals.
After starting "Data --> Schema Compare --> New Schema Comparison...", i can choose a database from a DropDown. Unfortunately there are some old references that i don't need anymore. How can i delete those entries?
I did recognize that the connections are stored in the Server Explorer. "View --> Server Explorer". The Data Connections stored there can be deleted.
You can manage them from the registry:
HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\12.0\SSDT\ConnectionMruList
Yes can view your added schemas in the "Server Explorer" in Visual Studio. Just, right-click the schema and delete it.
In the select schema connection window, click edit connection for the connection you don't want. The set it to a connection you already have and still want, this tricks it into removing itself.
It's the only way I've got them to remove!
For Visual Studio 2017:
Right click on your project in the Solution Explorer.
Select Properties.
Click the Settings option in the left menu pane.
Right click on the connection you want to remove.
KerPOW! Done! Gone!
For Visual Studio 2015 MRU connections are stored here: HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\14.0\ConnectionMruList
I am using Visual Studio 2012. I have clicked on Project and Select the name of project on dropdown menu e.g. MyDemo Properties. On the side menu click settings then you will find connection string listed in a table then Delete those you don't need.
You need to go into your web.config file and find the tag. You'll see all of your old and current connections in there you can delete the ones you no longer need.
None of the above worked for me in VS 2015. I could not find the registry entry mentioned. Only the following steps worked for me:
Delete any forms that rely on datasets you will delete.
Delete datasets that rely on the connections.
Remove all connection strings from app.config.
Remove all "settings" from the project properties setting tabs.
Delete all data connections in server explorer (View->Server Explorer).
Rebuild the project.
Now when you add a new Data Source all the connections in the dropdown are gone.
As another user mentioned above, deleting the data connections in the server explorer is not enough. When you exit VS and re-enter they come right back.
I changed some parameters in a Visual Studio C++ project, and now I don't remember how to "go back". Is it possible to reset the build settings?
I don't mean the IDE settings (menu Tools -> Import and Export Settings).
Am I the only person that can read?!
The only way I know how to reset a "Parameter in a Project's Settings",,,
Is to open the Project file(csproj, vcxproj) with a text editor, and remove the block defining that parameter.
If you wanted to reset the Allow Isolation value, you would delete this text.
<AllowIsolation>true</AllowIsolation>
When project files are loaded by visual Studio, values which are not explicitly defined in the file, are assumed to be using the default. This will only work if the property has a default value(can't change some).
NOTE: This is NOT the same as Deleting the value from the Project Properties Dialog in VS. That method writes a blank value to your project file.
The command "devenv /resetsettings" will restore Visual Studio back to its original factory state.
You can find list of devenv switches here.
You may be able to get the previous/saved version of your Visual Studio project (*.vcproj) from your software version control system.
As many wrote here before, there is a need to reset your visual studio to default settings. Just follow this: https://msdn.microsoft.com/en-us/library/ms247075(v=vs.90).aspx
Here is the awful method I used in Visual Studio 2022.
In "Property" pages, expand the individual configuration you want.
Click "All Options" and find the bold options you had changed.
To restore the defaults, click the options and select "<inherit from parent or project defaults>".
Click "Apply", then it will recover its original value.
Otherwise, you can compare the *.vcxproj with the project templates.