I removed my old projects in my visualstudio.com account but I can see them in the Visual Studio.
How can I delete a project/branch permanently?
deleting the project through wit admin command.
Sometimes while deleting through GUI the project still reflects , as the project may still be present in the database.
Related
I am trying to setup sanity in a Svelte & Routify project. was wondering if having an entire thing for sanity is necessary, I know you can publish the studio to .sanity.io, wondering why isn't everything online in the first place and not somethings local
Developing your studio locally allows you to make and test incremental changes. Other developers on your team can work from their own local studios and make their own changes as well. The deployed studio might be the tool used by members of your team who aren't developing the studio itself but are accessing or editing the content. They can work from that studio without seeing (potentially breaking) changes as they're being made, which would be the case if everything was edited online.
If you're familiar with how git works, you can think of a repo like you might have on GitHub. You can work on your repo locally—saving as you go by committing. No one else on your team can see these changes and they don't impact the remote repo. That's your local studio. Once you push your commits to GitHub, they're accessible to the rest of your team. That's your deployed studio.
I've never published an application on VB.NET but am reaching the point where I'll be able to release it.
In my project I have a database using Access. Right now I understand I can go to bin/debug to open up the copy of the database that is copied over. My concern is will this database copy be accessible once I publish the project?
I am using Visual Studio 2013. I have all components installed on my machine needed to run this application I am questioning. I have not completed the application to deploy for testing but some questions arose before completion that I need addressed now; to prevent overhauling later.
Here's how it should work when deployed to clients.
Client installs application which runs on desktop not windows store in WPF.
The application is per user and runs for all users on the local machine.
Each user needs to read and write data to a database file but it needs to be the same MDF being used. Therefore each process of the application, no matter the user session, on the same machine, all interact with the same database / same data.
Question: When adding the database to the project where will it be installed by default? In the applications program folder along with program? If so what restrictions exist to read/write to the database and are there any? I have added no extra security on my side. The info isn't private or critical.
Question: Would end users need to install any sort of SQL in order for the application to do this? If so I can package it with the install but this seems like alot of overhead during install.
If the MDF is installed per user how do I change this to install it once for all users?
Before saying so, yes this needs to be a database and not a file. Reasons I need not describe. I have considered alternative but this is by far the best solution so please no alternatives.
When you add mdf file to your project and set properly the value of Copy to Output Directory, it will be copied to the bin directory of your project whenever you build the project. When you create setup project for your app project, it will be by default copied to the folder where your app is installed. You can either specify different location in your setup project or copy the file to the desired location during the first run of your app.
There are several suitable folders in Windows, one possible choice is %PROGRAMDATA% C:\ProgramData folder, but it is by default read only for non-admin users. If you do not worry about security, go for %PUBLIC% C:\Users\Public. It is completely accessible for all users within interactive group.
I recommend to package LocalDB with your project. It can be installed silently with one line of code, though only with admin privileges. For non-admin click-once install you would have to use SQL CE, which is quite different and uses sdf files.
I think you should do it this way: include a seed database MDF file in the application and copy it to a %PUBLIC%\YourApp folder when the application first launches. Optionally include LocalDB install in your setup project.
The following references are being automatically added to my (console application) project:
Microsoft.Data.Tools.Schema.Sql.UnitTesting.dll
Microsoft.Data.Tools.Components.dll
My boss can't open the project on his machine.
As far as I know, I don't have any schema unit tests in the project, and there should be no reason for these references.
How can I resolve this? Might it be caused by the fact that I am running SSDT and my boss is not?
Update
The references can be removed via the References node in Solution Explorer, as well as via Project Properties -> References -> Unused References..., but when I next reopen the solution they are added back again.
This is a multi-project solution, but none of the other projects (WPF Application, 2 class libraries) have these added references.
Apparently this is being caused by SSDT, because when my boss installed SSDT on his machine he was then able to open the project without any problems.
Perhaps SSDT might be treating this as an SQL project, because there are a number of SQL files included in the project.
So I have a Visual Studio solution which contains 3 database (.dbproj) projects. These projects need to reference other sql projects from other solutions, which I have packaged and uploaded to nuget. How can I manage these external packages / references in Visual Studio within the dbproj's?
Right clicking the database project within visual studio doesn't give me the "Manage NuGet Packages..." option.
I can Manage NuGet Packages for Solution to at least download the required packages to the solution root but at the project level, where the references are required I'd have to manually manage the references within each projects' references and update manually any time the package is updated so the reference points to the correct versioned package directory.
Is there a better way to do this for dbproj references for database projects in Visual Studio??
I ended up following the same path, creating NuGet packages of the referenced databases and then manually (via command line) installing them at the standard \package location. Then correcting the database references manually in the IDE
There is a work item for this functionality, go vote it up. There is a fork of the functionality already developed that sounds like it is fairly feature complete. You might try it out.