Perfect for quickly generating Site Icons…
Just get this thing…
Download here (free)
Just an extremely quick and dirty trick I’ve used for a while now I thought I’d note down somewhere. It’s horribly inelegant and almost definitely very very wrong. You should definitely not do this.
In the ‘Site Assets’ library of a site, create an ‘htmlbits’ folder. In this folder, create a file with the format myFunction.html.bit. (The .bit extension stops various bits of SP machinery – such as SP Timer Jobs – from messing with your HTML)
Then, use these snippets in on a page with a Content Editor Webpart. Simply set the title of a Content Editor Webpart to the name of the HTML bit, set the Content Link to the .html.bit’s path, and set the title not to display. Your .html.bit file will be injected into the page, and SharePoint will not mess with your code!
This seems to bypass SharePoint’s HTML filtering, and it’s handy for debugging. A sort of nicely self-documenting and simple way for a designer simply trying to inject some HTML, CSS, and JS into a page.The deployment workflow is simple. Save and refresh.
I should also point out that it is potentially going to be frowned on by the security gurus at MS, who may see it as a bug. Dunno – not a security expert.
Anyway, once you have reached a solution using this trick, you should consider whether you can generalize what you’re doing into the master page, or the page layout, or deploy a custom solution using visual studio that can do this in a neater way. Don’t forget to delete the htmlbits folder when you’re done.
Forgot to note that Waldek Mastykarz has a different method which some may find more appropriate for their needs.
In the SharePoint branding & development communities, there has recently been a lot of buzz around the use of HTML5 features in SharePoint. Solutions like Kyle Schaeffer’s “v5.master“, or Bind templates are being deployed, and this has me a little concerned.
In my testing with IE9, I have found that various pieces of functionality do not work as expected with these solutions. The reason for this is as follows: SharePoint 2010’s IE9 support was tested and developed for IE9 running in IE8 compatibility mode, but these solutions typically disable the compatibility mode, breaking basic SharePoint functionality in the process.
Specifically, the tag…
<meta http-equiv="X-UA-Compatible" content="IE=8"/>
… has been either removed, or changed to one of these alternatives…
<meta http-equiv="X-UA-Compatible" content="IE=9"/>
<meta http-equiv="X-UA-Compatible" content="IE=edge"/>
It would be great if this worked, but the unfortunate truth is that there are various pieces of critical SharePoint functionality which simply don’t work if this is changed. Continue reading
(Not an advertisement) – If you’re interested in tinkering with SharePoint or CRM, there’s no easier way to get started than CloudShare. CloudShare provides hosted, pre-configured test and development environments that far surpass any VM you might run on your personal machine. It’s also great for collaborating on development/test/demo environments:
Well… Yeah. But don’t expect it to help much when it comes to SharePoint! We know that SharePoint vNext will have a Metro look and feel, but that doesn’t necessarily mean that SharePoint will be be joining Dynamics as a Windows-only ‘Metro Wall’ application. SharePoint has far too many legacy restrictions to become a pure Metro Wall + WinRT app. Reality check time:
So… hold up, and in the mean time, check out this neat client-side app stack diagram from the “Single Page Applications” guidance @ www.asp.net, and stay tuned for more tips!
Don’t forget to subscribe!
Microsoft has just demoed a working prototype of a Microsoft Dynamics
GP ERP, running on Windows 8, with a full Metro UI:
This is the first example of an enterprise app for the Windows 8 metro ‘wall’. More info about the demo is available at ZDNet.
The one hour keynote is available online behind a short registration form at msconvergence.com (demos start around 40 minutes in).