i designed one webpart using open xml sdk, how to create .wsp file manually without using vs2010.
Thanks in Advance,
Balaji
You need to create all xml files manually an then packages them as cab file with wsp extension.
Please follow this instruction from MSDN.
Related
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 an Addin. I have the .Addin file and DLL file. I need to know what the best way of distributing this to people would be?
It's mainly for people in the office.
The way I got it on a friends machine was to copy the .addin and .dll file to the Visual Studio Addin folder, however I had to open the .addin in Notepad++ and change the Assembly path to point to where the DLL is. How can I automate this so the plugin can be installed and have the Assembly area get updated to the install path?
Thanks for any help!
You can just put the assembly's filename in the .Addin file:
<Assembly>MyAddin.dll</Assembly>
No need for a full path.
I've created a VS2010 extension to manage a new type of project. I've created the VSIX file with the project and item templates inside, and everything works fine, i'm able to create a new project, syntax highlight, compile it, etc.
What i want to do now is to associate my files (.stadyn) to the VS2010, like a .cs file. I mean, give it an icon and open the VS2010 on a double-click.
Does anybody know how to deploy the extension and add those keys to windows registry?
Thanks in advance.
You have to possibilities.
Create an installer for your extension which is doing all the stuff.
Add the file associations when the extensions first starts.
I would prefer option one, since then you can also uninstall your extension and unregister the file associations and may be do other cleanup stuff. Also you could do other stuff during the install.
Edit:
Deployment is documented in the MSDN:
http://msdn.microsoft.com/en-us/library/ff363239.aspx
I need to build an add-on using Setup Project in VS 2010. The setup file should run sql script files that are inside of Setup project and copy/replace necessary assemblies into desired folder.
What is the best approach to do this?
Thank you.
The best option would be to implement a Custom Action on the installer and then do whatever you need to from there. You can embed the script files in the installer package by setting their type as "Embedded Resource" in the project. Maybe have a look at this page from the MSDN library:
http://msdn.microsoft.com/en-us/library/d9k65z2d%28v=vs.80%29.aspx
I am working on a Visual Sudio 2010 Setup Project to install an Entity Framework / SQL Compact app. The app needs to install an SDF file on the user's machine. As I understand the Microsoft guidance, I should install the SDF file to a company\application subfolder under C:\ProgramsData on the user's machine, which I have done in the setup project by creating a custom folder in the File System Editor with a DefaultLocation property of [CommonAppDataFolder]. All works well, and the SDF file is installed to C:\ProgramData\MyCompany\MyApp\MyFile.sdf.
Here is my problem: On the client machine, my app is throwing an EntityException with the following message: "SqlCeException: Access to the database file is not allowed." Sounds like a permissions issue.
Is there a way to set permissions on the SDF installation folders from within a VS Setup project? How would I do it? Any examples? Thanks for your help.
The answer is to create a small DLL that gets executed as a Custom Action by the Visual Studio Setup Project. There is a walkthrough on creating Custom actons here.