I am working with a VB 6.0 project. The project uses the packaging and deployment wizard. Where are deployment scripts saved when you use this wizard?
The deployment script is normally saved as a file alongside the project file with a .pdm extension.
The setup itself is created in whatever folder you told it to along with the support files required to rebuild the cabinet file.
To edit the deployment script, you can use a simple text editor like Notepad, or you can just re-run the wizard. I believe it uses the existing script as a base (but it's been ~10 years since I last used it).
Related
I am new to Xamarin and am trying to publish my application as a side loading package. I use VS2019 to publish the UWP application. The problem I have is that the AppInstaller file that Publish generates contains explicit references to folders on my computer. This, of course, works on my computer, but does not on anyone elses' computer. Here is an example from the AppInstaller file:
Uri="file:///c:/SpectrumApp/SpectrumApp.UWP.appinstaller"
I can write a powershell script to modify the App Installer file to contain the correct file path for a given system, but that seems like a workaround to some basic thing that I am doing wrong with the Publish capability built into VS2019.
My desktop app includes a SQLite database it uses internally. The contents of this database are stored in .SQL (text) files so that the entire DB can be recreated from scratch based on the source files. Running these scripts in the correct order is what I refer to as a "database build" in this context.
I am looking for ways to integrate this DB build into a Visual Studio solution. The ideal might be:
DB build is automatically re-run during a solution build whenever any .SQL file has changed, or if the target database does not exist
IDE integration - edit .SQL files right there inside VS2015
External program sqlite3.exe needs to be called to process each .SQL file
The output database file is deposited in the Debug\bin folder (or Release) just like any other build output
Processing errors captured in the Output pane
In other words - it behaves like a standard C# or C++ etc. project and build.
The only way I have turned up so far to do this might be to create an MSBuild script / project file. That may work but is not necessarily more advantageous than just running a batch file, and seems like it would lack IDE integration.
I was hoping there might be an existing VS project type which would accommodate this, but if it exists I haven't figured that out.
Build a SQLite database from Visual Studio?
If I understand you correct, you can include your database file in your project. Set the type to Content and CopyToOutputDirectory to Copy if newer, that will make sure the file is copied to your output directory and you can edit .SQL files inside VS2015.
Unload your project and add following into the project file .sqlproj:
<ItemGroup>
<Content Include="test.sql">
<CopyToOutputDirectory>PreserveNewest</CopyToOutputDirectory>
</Content>
</ItemGroup>
See the similar thread for some more details.
Hope this helps.
I have written a language and debug engine extension for visual studio, and I'm able to create a shell application from this extension. However, I'd like to include p4vs, as it's a pain trying to install that to the shell seperately, as the installer doesn't target shell applications.
I've discovered that this is indeed possible by following the instructions here.
But the basic gist is:
Create a subfolder in the Extensions/ subfolder
Rename the vsix extension to ".zip"
Using your favourite zip file manager, extract the files to your newly created extension folder from step 1
Delete the [Content_types].xml file
Optionally, edit the vsixmanifest file and add InstalledByMsi="true" to the element to prevent users from uninstalling the extension via the extension manager
I have completed packaging my application using VS installer and it works fine. However i want on double click some file extension like .vfx my application should launch automatically. Is there any direct property which i can set or i have to write script.
In the VS Setup Project, go to View->Editor->File types, and that's where you add your extension. There's some documentation here:
https://msdn.microsoft.com/en-us/library/4fcx9b75(v=vs.80).aspx
I have an issue. We are upgrading to VS 2012 at work. When we open a VS 2010 project Visual Studio converts the project. This is fine, because VS 2010 can still use the project (yay microsoft). However, there is a \Backup folder created in the solution directory. Is this being created as part of the migration? Is there any way to control it?
The reason I ask is that the process that makes this folder copies web.config files into the folder. If you then try to build the solution (these are MVC projects), we get a "It is an error to use a section registered as allowDefinition='MachineToApplication' beyond application level. This error can be caused by a virtual directory not being configured as an application in IIS." error. The cause is that there is a web.config file in a subfolder instead of the root folder. We did not make and do not want this change, and cannot figure out how to control it. Deleting the Backup\Web.config file fixes the error. Renaming it from web.config to web.config.bak fixes the problem.
I don't really want to have to personally open and convert every single project, and don't want random people bumping into this problem. Any idea how to either stop VS from creating the Backup folder, or how to make it create them in the my documents studio folder etc? I can't find any setting to control this and can't find any good info.
By chance, are you using the MvcBuildViews property to pre-compile your views at build time? If so, this is why you're encountering this (since it does the pre-compile in the same directory, it doesn't filter out any of the files below the project directory).
Note that you will also encounter this issue if you use the Publish feature for this project. Publish copies the web.config under your intermediate build output directory (by default, obj/) before and after applying web.config transforms.
The good news is that in VS2012, or in VS2010 with the latest Azure SDK installed, pre-compile is now supported for Web Application Projects (including MVC). These settings are currently in the project properties, under the Package/Publish Web tab.
(this doesn't directly address your question about the Backup folder, but it was too long for a comment.)
There is no way to control it that I found. We had to go ahead and run through and convert every project to 2012 and delete the backup folders to prevent any other team from running into it.