I need to deploy to "_catalogs/masterpage/" and "Style Library/" multiple jpg, css, javascript files
These files originate from a developer platform and are to be deployed to multiple platforms without using SharePoint Designer.
Apart from manually uploading multiple files in the /Forms/AllItems.aspx pages, is there another way to do this ?
I'm using SharePoint 2007
This is the exact purpose for solution packages:
The Windows SharePoint Services solution framework provides a way to bundle all the components for extending Windows SharePoint Services in a new file that is called a solution file. A solution file has a .CAB-based format but a .WSP extension. A solution is a deployable, reusable package that can contain a set of Features, site definitions, and assemblies that apply to sites, and that you can enable or disable individually. You can use the solution file to deploy the contents of a Web Part package, including assemblies, class resources, .dwp files, and other package components.
The two recommended tools for creating solution packages for SharePoint 2007 are WSPBuilder and STSDEV.
Related
Using Kentico for the first time and have inherited a version 7 project with custom web parts. There are folders with .cs files, folders with .dlls, and folders with .ascx/ascx.cs web parts. Most are active. Some are not.
What's the best way to assess what is used and what is compiled when looking at a Kentico instance? I'm trying to sort what Kentico stores for configuration, how Kentico knows what to compile, and how Kentico provides a pathway for custom ascx/ascx.cs webparts to use (via using) various libraries in folders on the Kentico instance folder structure.
Having worked with Kentico for quite a while it's pretty easy to identify them simply by looking in a few directories.
If you haven't worked with it before you might try to do a fresh install of version 7 which you can get from the Kentico Client Portal and compare them.
If the install was done with best practices, you can look in the following documentation and the "custom code" should be in the green and blue directories in the documentation.
There is an open-sourced utility called KInspector (it`s made by Kentico consulting team). This utility should show you your custom code (among the others) in Kentico instance (afaik it is in the Analysis module).
I'm developing an Office 365 Mail Add-in in Napa and want to set the app icon. There is a manifest XML file that can include an IconUrl element, but the Napa platform doesn't provide an avenue for uploading my manifest.
Is there a way to set the icon using Napa? If not, what can I use to deploy a version of my add-in to my test account with the updated manifest?
I would highly recommend that if you are ready to custom your manifest, you should consider using Visual Studio 2015 Community with Office Developer Tools. Napa is a lightweight playground for exploring and trying out the Office Add-ins quickly and I think you'll find that you have a lot more power in VS.
If you are using a mac, download your project from Napa and you can use any preferred development environment (instructions on how to debug with a text editor).
Thanks for asking and please feel free to reach out again if you have any more questions!
Nicole, Program Manager for Microsoft Office Development Tools
Generally you would reference the icon image in the manifest just as you would reference image files in .html pages in your solution. For example, store the icon in the Contents or Images folder and reference it using virtual paths. It has to be stored on the web server whether your .html, .js and .css files are located.
Note that the only place you really upload your manifest is within the Addin management pages within your Mailbox or via the Exchange Admin Center pages.
I have access to a working ASP.NET MVC 4 website through FTP but do not have the Visual Studio project file. Using these files can I create a Visual Studio project file?
If you have access to all the class files, views etc but are just missing the solution/project file then technically you can wrap them up in an empty project but it would still be a different project.
If you only have access to the published output (the views and JavaScript) then in short the answer is no, not without trying to reverse engineer the dll which I have heard is possible but have never tried myself.
I am working with nuget and find it excellent with my MVC4 project. I use it for all my external dependencies.
I have run in to one small problem with it. For example, installing the jQuery package, it places the jQuery files in to the Scripts folder. My preference is that it places the javascript files in to a libraries folder within scripts. So instead of
Scripts/jquery-1.8.3.js
I want to place it in
Scripts/libraries/jquery-1.8.3.js
Yes I can manually move it but then I lose the features of nuget. Any way that I can direct where a package places the files like this?
This is not supported yet
dupe of
NuGet scripts to different directory
, nuget codeplex issue is here http://nuget.codeplex.com/workitem/1914
Is there an effective way to share visual assets between different projects?
This would include images, CSS and JavaScript.
I've looked at the following Stack Overflow questions which don't seem to answer this:
Sharing css/javascript/images between different projects in Visual Studio
Visual Studio - Resource (CSS/JS/Images) sharing between web projects
Handling common JavaScript files in Visual Studio 2010
We make use of TFS, not sure if that might have something we can use?
There's nothing built-in ASP.NET MVC that will allow you to generate links to other ASP.NET applications. All the helpers work with relative controller actions for the current application. If all your static files are located inside another ASP.NET application (a sort of custom CDN) then you could define the base location of this application in your web.config and then build custom helpers that will serve those resources:
#Html.Resource("/foo.js", "text/javascript")
and the custom helper will generate an absolute url to this external resource.
A handy solution is to create a "Solution folder" as shown in Erik Philips's solution.
Basically "Solution folder" is just a common share folder created in your solution that contains all shared files, then you refer these files in your project(s) as links. For all practical purposes these share files could be used in your site(s) as if they were present in your local site folder.
I have been struggling with this same problem, and I found that the best solution for me was simply to create a "holder" project for the assets files, and with the help of pre-build events just copy all the files into the projects that require them. This way you just need to edit them in the "holder" project, but they will always be in-sync as long as you dont touch them in the other projects.