I am trying to install Twitter-Bootstrap 3 on a 2013 SharePoint site. I can't seem to install it properly (Col-- class isn't recognized therefore pages aren't responsive) and I can't find any documentation that may help me. Any help would be greatly appreciated...
There are many 3rd party sources available for Twitter Bootstrap 3.0.0 integrated into SharePoint 2013 for a site with Publishing enabled.
You can check:
https://responsivesharepoint.codeplex.com/releases/view/112845
http://social.msdn.microsoft.com/Forums/sharepoint/en-US/1db1094e-6f83-418a-ba6f-c339a67e59e0/twitter-bootstrap-sharepoint-2013?forum=sharepointcustomization
Related
We are planning to create setup file for our project, our research lead us to:
InstallAwere 18
InstallShield 2013
We have some requirements that must be supported:
Windows Server 2012
Able to run other MSI/EXE
Full support for patches/updates
Run Powershell script
Database support (Create db/Execute sp)
Web site deployment
Nice to have:
- Windows features identification (run installation if necessary)
- Web installer (small package that will download all the necessary components)
Did I miss any other product on the market that can support all this? And the final question is what would you suggest for our setup package between these two?
Firsthand experience would be great.
Actually there is another application you can use for creating setup packages. It is Advanced Installer.
I'm using it for several years and it is really easy to use. I think it can help you with all of your requirements. They also have a great support team.
i think that InstallAware is more power full than InstallShield
look: http://www.installaware.com/compare-with-otherinstall-tools.htm
I am new to sharepoint and installshield. My responsiblity is to build and deploy the sharepoint solution as a package using istallsheild. Previously I was using solution package wsp and content database restoration. But now the client wants to deliver the total solution i.e. dlls, ascx files, xml files, servce files(.cs), feature files using installsjield from development server to another (test and/or client) server.
Can any body help me on this: how to do the sharepoint deployment using installshield?
thanks in advance.
I presume you are using SharePoint solutions to package dll's, ascx and xml files for deployment to a sharepoint server. These solutions are built using a tool like WSPBuilder.
If not: YOU SHOULD!
If so: Why not use SharePoint Installer? It is an installer wrapper around a .wsp (SharePoint solution) file. It will check for the existence of a sharepoint installation, if the required services are started etc.
For deployment to a test machine: Why would you need the .cs files? If you want to test (debug) code on a test machine, I suggest you use either continuous integration using a tool like CruiseControl.NET, or just install Visual Studio on the test machine (which I presume to be a dev test, not a client test machine) and get the latest version, do a build, then roll out the solution.
And what do you mean with "client" server? is there some windows app that's communicating with sharepoint included in the installer? If so, I suggest separating the SharePoint solution from the actual windows app. They might share DLL's but are not supposed to be in the same installer.
We are using a tool (open source - saf.codeplex.com) to automate the Sharepoint components using MSBuild/Features/STSADM etc. Recently they have upgraded this to use WIX so that we can deploy any SharePoint components.
saf.codeplex.com
It has got an very good documentation and also we got a good support in fixing and implementing the SharePoint automated deployment in our premise.
Thanks
BalamuruganK
i have project in C#, ASP.Net and SharePoint. i want to deploy it usung VS2005 Setup and Deployment tool (As i am not allowed to use any otther software). Can i deploy the Sharepoint part like webparts in VS2005. please tell me what steps i have to take for sharepoint.
All Suggestions are welcome.
Thanks in advance
In short using the VS2005 Setup & Deployment for deploying items to SharePoint is not recommended or not supported.
SharePoint by itself has it well know deployment way called SharePoint Solutions or WSP file. Almost all the items you will want to deployed to SharePoint can be done using WSP(this includes WebPart as well, not only webpart it will allow to add a safe control entry to WebConfig as well). As per your question you are not allowed to use any other tool. To create WSP solution you will not need any extra tool. You can create a WSP file just with notepad (ddf file) & makecab.exe (its avaliable in most of the windows OS).
If you want to make it life simpler try out WSPBuilder and to install the WSP to sharepoint you can use the STSADM command or SharePointInstaller I have been using these tools for past 3 years and they work like charm.
You also have another option of doing it in the Visual Studio just by installing this template VSeWSS version 1.2!
There were a lot of promises and hopes, but did MS actually get around to including ASP.Net AJAX in either WSS3 SP1 or MOSS SP1? None of the release notes mention it...
No, ASP.Net AJAX is not included in either Service Pack.
ASP.Net AJAX was included with .net 3.5.
As far as I remember it wasn't included in WSS3 or MOSS SP1.
BTW WSS3 & MOSS SP2 is now out (and I don't believe it was included in that either.)
It's not that hard to get setup, you just need to make some interesting additions to your web.config, and master pages.
In my experience ASP.NET AJAX must be installed by itself (it hasn't been included in anything I have installed). Here is the download link for the installer.
Follow this article to get it loaded into the SharePoint web.config files.
In January, MS released a CTP of VS Extensions for SharePoint v1.3. Has anyone used these? What have your experiences been?
We used the previous version and did not like how much was hidden/abstracted from the developers. We eventually abandoned the extensions and create our own WSP's with MakeCab.exe.
...Peter
The install of the website that runs the webservices completely failed and I could never get it to work so I uninstalled it.
Till today I didn't encounter any problems with VSeWSS 1.3. except some issues with the VSeWSS's web service, which were related to a name resolving problem of my PC.