Hot answers tagged

3

Best way to move SharePoint solutions is using .wsp file which is created as you deploy any solution just copy from development, paste in production and then add and deploy solution there by power shell. To move list use export functionality in central admin of development and then import the .cmp file in production. done!


2

There is an easier way to update a farm solution, and that is the Update-SPSolution cmdlet. If your changes or bugfixes are primarily in the code-behind of the webpart, this will successfully update the .dll or any .aspx/.ascx files associated with the webpart without having to do a full retraction and re-installation. Please note that the documentation ...


2

Dylan's answer is correct - you need to reset IIS so that the Web Worker Processes can pick up the new DLLs. I'd also like to share a method I've used to get around this in the past - if your bug fixes are only asset-related (i.e., JavaScript, CSS) and are deployed to the Layouts mapped directory, then you can edit the files by browsing to the Layouts ...


1

Unfortunately in this scenario that you described there is no way to update the package without the end user notice the maintence. In a mid-term solution, i strongly recommend you to gradually migrate your solutions to a Sharepoint Provider-hosted Add-Ins/Apps, then you can make your changes without stop the entire site. Here some links to help you: ...


1

What about a normal list but make a custom field where you can add the different properties and a field to add attachements (like your pdf/excel)? This is achieved by adding a 'add attachement field' in list design mode.


1

You could use a custom list for products. Create columns for that list, so every item in that list will describe your product (Product Title, Category, description, price, version, anythingelse). For every item in sharepoint list you could add attachments.



Only top voted, non community-wiki answers of a minimum length are eligible