In sharepoint 2010 there is a feature that allows a site owner to view all checked out files using the option "Manage files which have no checked in version".
I noticed that when a pdf file in the document library is checked out, either on purpose or accident, the pdf is not listed in the "managed files which have no checked in version".
Anyone familiar with not being able to managed known checked out files not being listed in the "Manage files which have no checked in version"?
"Manage files which have no checked in version" lists only documents which have been uploaded but have never been checked in. For example if a file is in version 1.0 then its checked out that file will not be listed in "Manage files which have no checked in version".
Related
My goal is install VSTO Outlook Addin for all users on local PC instead of current user. I used Publish method from Visual Studio and result is exe file, which means ClickOnce method. (not posible for install for All)
Well i start my research i found Wix.
My first question is, when i create Build from Visual Studio from my VSTO addin, i have 2 dirs and 20 files, is possible to assign dirs in product.wxs file in WIX Directory ref?
Second question, when files and dirs are "installed" to target directory, (program files for example) how can be VSTO be assigned to Outlook ? Its becouse to add VSTO to registry HKLM ?
Im asking if im closer to my goal
Not sure if I understood your first question but I will try to answer it anyway. The only files you have to bring to a user's PC are those that are located under bin/Release folder, except for those that have the *.pdb extension. There are 2 ways how you can add them into the installation:
First way is to manually add each file you want to include in your installation as the file component in you Product.wxs. You can find a good example of that in their official tutorial.
Second way is to utilize the harvest tool (Heat) from Wix Toolset. This tool can generate a list of components automatically during a build.
As for your second question. To make Word or Outlook see your add-on you have to create an entry in Windows registry during installation. For example for Microsoft Word you have to create a new key HKLM\Software\Microsoft\Office\Word\Addins\MySuperAddOn with the following entries:
Entry
Type
Value
Description
REG_SZ
Required. A brief description of the VSTO Add-in. This description is displayed when the user selects the VSTO Add-in in the Add-Ins pane of the Options dialog box in the Microsoft Office application.
FriendlyName
REG_SZ
Required. A descriptive name of the VSTO Add-in that is displayed in the COM Add-Ins dialog box in the Microsoft Office application. The default value is the VSTO Add-in ID.
LoadBehavior
REG_DWORD
Required. A value that specifies when the application attempts to load the VSTO Add-in and the current state of the VSTO Add-in (loaded or unloaded). By default, this entry is set to 3, which specifies that the VSTO Add-in is loaded at startup. For more information, see LoadBehavior values. Note: If a user disables the VSTO Add-in, that action modifies LoadBehavior value in the HKEY_CURRENT_USER registry hive. For each user, the value of the LoadBehavior value in the HKEY_CURRENT_USER hive overrides the default LoadBehavior defined in the HKEY_LOCAL_MACHINE hive.
Manifest
REG_SZ
Required. The full path of the deployment manifest for the VSTO Add-in. The path can be a location on the local computer, a network share (UNC), or a Web server (HTTP). If you use Windows Installer to deploy the solution, you must add the prefix file:/// to the manifest path. You must also append the string |vstolocal (that is, the pipe character | followed by vstolocal) to the end of this path. This ensures that your solution is loaded from the installation folder, rather than the ClickOnce cache. For more information, see Deploy an Office solution by using Windows Installer. Note: When you build a VSTO Add-in on the development computer, Visual Studio automatically appends the
You may want to read the official documentation to see more details.
Wix Toolset does allow to do that as well. You have to declare the RegistryKey component in your Product.wxs.
I made a simple checklist desktop app in Visual Studio 2015, and I'm ready to share it with the world. Problem is that I don't know how to make an installer for it that I can share online. I have an installer exported, but it is Visual Studio's default ClickOnce installer, which won't work when I remove it from its original location
Is there a way I can package it so I can upload it somewhere and then share it? Do I need to code my own, or there some add-in or tool that will do it for me?
Once you have the installer extension this should help you to get started, as the name implies:
https://www.simple-talk.com/dotnet/visual-studio/getting-started-with-setup-projects/
Have a look at this older post of mine:
What you can do,open the project as if going to edit it, just go to "Project" then "Publish(Whatever-your-work's-name-is).vb at the bottom. Then use the wizard to finish. At the end, say you saved your exe on the desktop, three files will appear.
"Whatever-your-work's-name-is".exe And its icon shape varies.
A folder called "Application Files"
And a "setup.exe" Its icon a like a CD on something.
For the first time, click on setup.exe and open the app. From then on, the "Whatever-your-work's-name-is".exe will open normally. I usually store all three on a zipped folder, which I upload on my website and can be downloaded from there.
To get a better example, vist my website.
I use this website to store my files for backup.
You can get the MS Installer extension from here... There's one for VS 2013 too.
(Credit to peterG for commenting this)
I have looked around on many Youtube videos but I was not able to find a good one that made sense since they were either old or not clear in explaining it. So I decided to come here. I'm so sorry for my bad grammar and not being able to explain things too well.
I can't figure out on how to use "Microsoft Visual Studio 2015 Installer Projects" extension, since I do not know what are files to add into the "Application Folder" section. For the User Desktop, I am guessing it would be just a shortcut and the .ico file with it just excluded so the shortcut can have the icon with it also.
Thanks in advance,
Ryan
You can put your project output(.exe) and all of its .dll in the Application Folder. For the shortcut, you can set the application's icon on the application properties:
http://i.stack.imgur.com/5vtzz.png
Once you're finished, you can build the project. And you will see a installer on the installer project's debug folder.
See if this helps, it's old but still applies:
https://www.simple-talk.com/dotnet/visual-studio/getting-started-with-setup-projects/
I've created my first Office Add-in using Visual Studio. It targets the 4.0 .Net framework and was created using the new VS 2012. I need to distribute/install this project on various 32-bit XP and 64-bit Windows 7 computers around the office. So I configured the project to be installed on XP (which was my first speed bump because I didn't realize VS 2012 needed an update in order to make a solution that was XP compatible). Now that I have a valid win32 application, I am getting another error:
The following error occurred attempting to install 'C:\filepath...\Import Contacts.vsto':
"No application is associated with the specified file for this operation."
After doing some digging, I think I need to install the Microsoft Visual Studio Tools for Office Runtime on the client computer. To do this, I would like to use the prerequisites properties for the project. So I read up on creating custom prerequisites using some noteworthy sites (e.g, Creating Bootstrapper Packages, Application Deployment Prerequisites, Adding Custom Prerequisites, and Creating a Bootstrapper package for Office 2013 in Visual Studio 2012). I created the files according to that last URL (even though I'm not sure it pertains to the package I need just yet), but it is not appearing in the dialog box under Project > Properties > Publish > Prerequisites
If you read the article, it says the VS prerequisites dialog box should automatically update once I restart VS 2012, which I did but to no avail. I know I'll need to use this feature again in the future, so I would really like to know what I'm doing wrong and fix this. Please help! And I promise to quickly give the ACCEPT to whoever helps me fix this problem! Thank you in advance.
I didn't have any problems following the directions given in the web page and got the bootstrapper added to the Prerequisites dialog. However, there are plenty of possible ways to get it wrong. Some possibilities:
Triple-check the folder you added these files to. Be sure that you picked Program Files (x86) on a 64-bit version of Windows and not Program Files. And be sure that you now see the added VSTOR40 folder along with the other existing bootstrapper folders, like ReportViewer and VBPowerPacks.
You do not have write permission to this folder, UAC prevents copying files there. Be sure that you managed to copy them from, say, an elevated command prompt. Right-click the Command Prompt shortcut and click "Run as Administrator".
If you created the .xml files with Notepad then make sure you didn't accidentally saved them with the .txt extension. If necessary, put Explorer in "programmer mode" so you can see the filename extensions. Control Panel + Folder Options, View tab, untick the "Hide extensions for known file types" checkbox. If you now see product.xml.txt then rename the file to product.xml, same for package.xml.txt
If you created the .xml files with Notepad then be sure to save the file in UTF-8 encoding. File + Save As, Encoding combobox.
For all those who still may face similar issue I think that I found the cause of this issue. It seems that copying folder with custom bootstrapper package (and all necessary files in it) does not "refreshes" the list of available packages. Only when i went through this walkthrough and manually created folder in %Programfiles%\Microsoft SDKs\Windows\v7.0A\Bootstrapper\Packages\ for sample package from this walkthrough my package has shown
I have a solution which can be deployed for SharePoint 2007 and SharePoint 2010. There are common files like .css files and images. When I am deploying solution for SP2010 I use mapped folder (_Layouts). And this folder have to copy my files to the server. The point is that I don't want to copy the same files to this folder. And I add them as a link. But Visual Studio does not want to copy files to destination folder.
If I understand you correctly, you want to deploy linked files. This is not just a SharePoint limitation, but a Visual Studio limitation with web projects. I believe the same limitation exists for SharePoint projects. Please refer to the following link:
https://connect.microsoft.com/VisualStudio/feedback/details/665257/
I've resolved this issue. Just removed the links and added real files.