<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Patrick's Bytes</title>
	<atom:link href="http://patrickyong.net/feed/" rel="self" type="application/rss+xml" />
	<link>http://patrickyong.net</link>
	<description>Techie for the past 30 years...</description>
	<lastBuildDate>Sat, 27 Apr 2013 01:10:23 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>SharePoint 2013 for web designer</title>
		<link>http://patrickyong.net/2013/04/27/sharepoint-2013-for-web-designer/</link>
		<comments>http://patrickyong.net/2013/04/27/sharepoint-2013-for-web-designer/#comments</comments>
		<pubDate>Sat, 27 Apr 2013 01:10:23 +0000</pubDate>
		<dc:creator>Patrick</dc:creator>
				<category><![CDATA[Sharepoint]]></category>
		<category><![CDATA[sharepoint2013]]></category>

		<guid isPermaLink="false">http://patrickyong.net/?p=1894</guid>
		<description><![CDATA[SharePoint Server 2013 has make life for web designers easier by not forcing them to learning .NET and SharePoint. They can pop open Dreamweaver to create a site template, then upload it to SP 2013 Design Manager and have Design &#8230; <a href="http://patrickyong.net/2013/04/27/sharepoint-2013-for-web-designer/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>SharePoint Server 2013 has make life for web designers easier by not forcing them to learning .NET and SharePoint. They can pop open Dreamweaver to create a site template, then upload it to SP 2013 Design Manager and have Design Manager take care everything for them. They will never have to touch SharePoint Designer 2013.</p>
<p>&nbsp;</p>
<p>I haven&#8217;t found a full tutorial for designers yet but there are some good blog posts out there to illustrate how Design Manager works for designers.</p>
<p>&nbsp;</p>
<p>Begin with this one</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p><a href="http://bniaulin.wordpress.com/2012/07/18/sharepoint-2013-design-manager-convert-html-to-master-page"><span style="text-decoration: underline;"><span style="color: #0000e9; font-family: Calibri; font-size: medium;"><span style="color: #0000e9; font-family: Calibri; font-size: medium;"><span style="color: #0000e9; font-family: Calibri; font-size: medium;">http://bniaulin.wordpress.com/2012/07/18/sharepoint-2013-design-manager-convert-html-to-master-page</span></span></span></span></a><span style="font-family: Calibri; font-size: medium;"><span style="font-family: Calibri; font-size: medium;">/</span></span></p>
<p>&nbsp;</p>
<p>More details here</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p><a href="http://www.learningsharepoint.com/2013/03/25/add-an-html-master-page-to-sharepoint-2013-using-design-manager"><span style="text-decoration: underline;"><span style="color: #0000e9; font-family: Calibri; font-size: medium;"><span style="color: #0000e9; font-family: Calibri; font-size: medium;"><span style="color: #0000e9; font-family: Calibri; font-size: medium;">http://www.learningsharepoint.com/2013/03/25/add-an-html-master-page-to-sharepoint-2013-using-design-manager</span></span></span></span></a><span style="font-family: Calibri; font-size: medium;"><span style="font-family: Calibri; font-size: medium;">/</span></span></p>
<p>&nbsp;</p>
<p>More tutorials</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p><a href="http://www.learningsharepoint.com/2013/03/25/sharepoint-2013-design-manager-tutorials"><span style="text-decoration: underline;"><span style="color: #0000e9; font-family: Calibri; font-size: medium;"><span style="color: #0000e9; font-family: Calibri; font-size: medium;"><span style="color: #0000e9; font-family: Calibri; font-size: medium;">http://www.learningsharepoint.com/2013/03/25/sharepoint-2013-design-manager-tutorials</span></span></span></span></a><span style="font-family: Calibri; font-size: medium;"><span style="font-family: Calibri; font-size: medium;">/</span></span></p>
]]></content:encoded>
			<wfw:commentRss>http://patrickyong.net/2013/04/27/sharepoint-2013-for-web-designer/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>SharePoint 2013 Executing REST API on the browser</title>
		<link>http://patrickyong.net/2013/01/01/sharepoint-2013-executing-rest-api-on-the-browser/</link>
		<comments>http://patrickyong.net/2013/01/01/sharepoint-2013-executing-rest-api-on-the-browser/#comments</comments>
		<pubDate>Tue, 01 Jan 2013 15:48:39 +0000</pubDate>
		<dc:creator>Patrick</dc:creator>
				<category><![CDATA[Sharepoint]]></category>
		<category><![CDATA[sharepoint2013]]></category>

		<guid isPermaLink="false">http://patrickyong.net/2013/01/01/sharepoint-2013-executing-rest-api-on-the-browser/</guid>
		<description><![CDATA[SharePoint 2013 provides REST API via _api/web interface. You can try it out in your browser by typing http://{your site}/_api/web However if you are using IE, you get a nasty reply that looks like below screenshot Basically IE comes with &#8230; <a href="http://patrickyong.net/2013/01/01/sharepoint-2013-executing-rest-api-on-the-browser/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>SharePoint 2013 provides REST API via _api/web interface. You can try it out in your browser by typing <a href="http://{your">http://{your</a> site}/_api/web</p>
<p>However if you are using IE, you get a nasty reply that looks like below screenshot</p>
<p><a href="http://patrickyong.net/wp-content/uploads/2013/01/Screen-Shot-2012-12-27-at-12.06.15-AM.png"><img style="background-image: none; border-right-width: 0px; padding-left: 0px; padding-right: 0px; display: inline; border-top-width: 0px; border-bottom-width: 0px; border-left-width: 0px; padding-top: 0px" title="Screen Shot 2012-12-27 at 12.06.15 AM" border="0" alt="Screen Shot 2012-12-27 at 12.06.15 AM" src="http://patrickyong.net/wp-content/uploads/2013/01/Screen-Shot-2012-12-27-at-12.06.15-AM_thumb.png" width="503" height="195"></a></p>
<p>Basically IE comes with a feed reader that doesn&#8217;t render the REST feed properly. You can turn off this reader by going to <strong>Internet Options</strong> –&gt; <strong>Content</strong> then click on <strong>Settings</strong> under <strong>Feeds and Web Slices</strong> section. Make sure <strong>Turn on feed reading view</strong> is unchecked</p>
<p><a href="http://patrickyong.net/wp-content/uploads/2013/01/Screen-Shot-2012-12-27-at-12.13.09-AM.png"><img style="background-image: none; border-right-width: 0px; padding-left: 0px; padding-right: 0px; display: inline; border-top-width: 0px; border-bottom-width: 0px; border-left-width: 0px; padding-top: 0px" title="Screen Shot 2012-12-27 at 12.13.09 AM" border="0" alt="Screen Shot 2012-12-27 at 12.13.09 AM" src="http://patrickyong.net/wp-content/uploads/2013/01/Screen-Shot-2012-12-27-at-12.13.09-AM_thumb.png" width="352" height="366"></a></p>
<p>Then restart IE and see your REST call renders nicely on IE</p>
<p><a href="http://patrickyong.net/wp-content/uploads/2013/01/Screen-Shot-2012-12-27-at-12.14.00-AM.png"><img style="background-image: none; border-right-width: 0px; padding-left: 0px; padding-right: 0px; display: inline; border-top-width: 0px; border-bottom-width: 0px; border-left-width: 0px; padding-top: 0px" title="Screen Shot 2012-12-27 at 12.14.00 AM" border="0" alt="Screen Shot 2012-12-27 at 12.14.00 AM" src="http://patrickyong.net/wp-content/uploads/2013/01/Screen-Shot-2012-12-27-at-12.14.00-AM_thumb.png" width="415" height="391"></a></p>
]]></content:encoded>
			<wfw:commentRss>http://patrickyong.net/2013/01/01/sharepoint-2013-executing-rest-api-on-the-browser/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>App for SharePoint 2013 &#8211; Unable to login to app site even after credential prompt</title>
		<link>http://patrickyong.net/2012/12/26/app-for-sharepoint-2013-unable-to-login-to-app-site-even-after-credential-prompt/</link>
		<comments>http://patrickyong.net/2012/12/26/app-for-sharepoint-2013-unable-to-login-to-app-site-even-after-credential-prompt/#comments</comments>
		<pubDate>Tue, 25 Dec 2012 17:39:23 +0000</pubDate>
		<dc:creator>Patrick</dc:creator>
				<category><![CDATA[Sharepoint]]></category>
		<category><![CDATA[sharepoint2013]]></category>

		<guid isPermaLink="false">http://patrickyong.net/?p=1880</guid>
		<description><![CDATA[When you deploy or debug an app for SharePoint, you will get multiple user credential challenge [in my case I am using NTLM authentication] but fail to login. This is caused by the loopback check feature exists since Windows Server &#8230; <a href="http://patrickyong.net/2012/12/26/app-for-sharepoint-2013-unable-to-login-to-app-site-even-after-credential-prompt/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>When you deploy or debug an app for SharePoint, you will get multiple user credential challenge [in my case I am using NTLM authentication] but fail to login. This is caused by the loopback check feature exists since Windows Server 2003 SP1. To disable this loopback check, open up powershell and execute the following command. Note: Do this only on your development machine.</p>
<pre>New-ItemProperty HKLM:\System\CurrentControlSet\Control\Lsa -Name "DisableLoopbackCheck" -Value "1" -PropertyType dword</pre>
]]></content:encoded>
			<wfw:commentRss>http://patrickyong.net/2012/12/26/app-for-sharepoint-2013-unable-to-login-to-app-site-even-after-credential-prompt/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Setting up SharePoint 2013 for Apps Development</title>
		<link>http://patrickyong.net/2012/12/25/setting-up-sharepoint-2013-for-apps-development/</link>
		<comments>http://patrickyong.net/2012/12/25/setting-up-sharepoint-2013-for-apps-development/#comments</comments>
		<pubDate>Tue, 25 Dec 2012 13:30:27 +0000</pubDate>
		<dc:creator>Patrick</dc:creator>
				<category><![CDATA[Sharepoint]]></category>
		<category><![CDATA[sharepoint2013]]></category>

		<guid isPermaLink="false">http://patrickyong.net/?p=1877</guid>
		<description><![CDATA[This post shows how to create the nessacery service applications for SharePoint Apps. However when I click on Configure Apps URLs on Central Administration site, I got a &#8220;the subscription settings service and corresponding application&#8230; &#8221; error message and cannot &#8230; <a href="http://patrickyong.net/2012/12/25/setting-up-sharepoint-2013-for-apps-development/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>This <a href="http://technet.microsoft.com/en-us/library/fp161236(v=office.15).aspx">post</a> shows how to create the nessacery service applications for SharePoint Apps.</p>
<p>However when I click on Configure Apps URLs on Central Administration site, I got a &#8220;the subscription settings service and corresponding application&#8230; &#8221; error message and cannot proceed. It turns out I also need to create a Subscription Service Application shown in the post below</p>
<p>http://blogs.technet.com/b/speschka/archive/2012/07/23/setting-up-the-subscription-settings-service-application-in-sharepoint-2013.aspx</p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://patrickyong.net/2012/12/25/setting-up-sharepoint-2013-for-apps-development/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Sharing SharePoint 2010 and ASP.NET 4.0 User Credential</title>
		<link>http://patrickyong.net/2012/11/04/sharing-sharepoint-2010-and-asp-net-4-0-user-credential/</link>
		<comments>http://patrickyong.net/2012/11/04/sharing-sharepoint-2010-and-asp-net-4-0-user-credential/#comments</comments>
		<pubDate>Sun, 04 Nov 2012 10:31:00 +0000</pubDate>
		<dc:creator>Patrick</dc:creator>
				<category><![CDATA[Sharepoint]]></category>
		<category><![CDATA[sharepoint 2010]]></category>

		<guid isPermaLink="false">http://patrickyong.net/?p=1868</guid>
		<description><![CDATA[Many people have their custom ASP.NET application embedded as a IFRAME inside SharePoint. When you do this, you might also want to take advantage of creating a &#8216;Single Sign On&#8217; experience for your users so that the ASP.NET doesn&#8217;t challenge &#8230; <a href="http://patrickyong.net/2012/11/04/sharing-sharepoint-2010-and-asp-net-4-0-user-credential/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>Many people have their custom ASP.NET application embedded as a IFRAME inside SharePoint. When you do this, you might also want to take advantage of creating a &#8216;Single Sign On&#8217; experience for your users so that the ASP.NET doesn&#8217;t challenge the user for password again. You can make use of SharePoint SSO to achieve this but if you are using SharePoint 2010 Foundation you will run into problem so this is a solution I found online that works.</p>
<p>I got the guide from <a href="http://samsonfr.wordpress.com/2012/07/24/intgrer-une-application-asp-net-mvc-3-sous-un-site-web-iis-hbergeant- sharepoint-server-2010/">this French blog</a> and got Google to translate for me. Certain parts are not clear [due to mistake in translation] so I repost it here</p>
<p>Create a new App Pool that share the same User Credential with the SharePoint site.</p>
<p>Copy the content of your ASP.NET 4.0 web app into a folder under the SharePoint site. In my case it will be C:\inetpub\wwwroot\wss\VirtualDirectories\8080\</p>
<p>Inside IIS Manager convert this folder into a web application.</p>
<p>Go inside C:\Windows\Microsoft.NET\Framework64\v2.0.50727\CONFIG and open the Web.config (.NET version here maybe different)</p>
<p>Before anything else right after the &lt;?xml&gt; opening node add the following (in case you dont have configSections defined already, else append to it)</p>
<pre>&lt;configSections&gt;
    &lt;sectionGroup name="system.web.extensions" type="System.Web.Configuration.SystemWebExtensionsSectionGroup, System.Web.Extensions, Version=3.5.0.0,
Culture=neutral, PublicKeyToken=31bf3856ad364e35"&gt;
      &lt;sectionGroup name="scripting" type="System.Web.Configuration.ScriptingSectionGroup, System.Web.Extensions, Version=3.5.0.0, Culture=neutral,
PublicKeyToken=31bf3856ad364e35"&gt;
        &lt;section name="scriptResourceHandler" type="System.Web.Configuration.ScriptingScriptResourceHandlerSection, System.Web.Extensions, Version=3.5.0.0,
Culture=neutral, PublicKeyToken=31bf3856ad364e35" requirePermission="false" allowDefinition="MachineToApplication" /&gt;
        &lt;sectionGroup name="webServices" type="System.Web.Configuration.ScriptingWebServicesSectionGroup, System.Web.Extensions, Version=3.5.0.0,
Culture=neutral, PublicKeyToken=31bf3856ad364e35"&gt;
          &lt;section name="jsonSerialization" type="System.Web.Configuration.ScriptingJsonSerializationSection, System.Web.Extensions, Version=3.5.0.0,
Culture=neutral, PublicKeyToken=31bf3856ad364e35" requirePermission="false" allowDefinition="Everywhere" /&gt;
          &lt;section name="profileService" type="System.Web.Configuration.ScriptingProfileServiceSection, System.Web.Extensions, Version=3.5.0.0,
Culture=neutral, PublicKeyToken=31bf3856ad364e35" requirePermission="false" allowDefinition="MachineToApplication" /&gt;
          &lt;section name="authenticationService" type="System.Web.Configuration.ScriptingAuthenticationServiceSection, System.Web.Extensions, Version=3.5.0.0,
Culture=neutral, PublicKeyToken=31bf3856ad364e35" requirePermission="false" allowDefinition="MachineToApplication" /&gt;
        &lt;/sectionGroup&gt;
      &lt;/sectionGroup&gt;
    &lt;/sectionGroup&gt;
  &lt;/configSections&gt;</pre>
<p>After that go to the web.config of the SharePoint site, comment out the exactly same whole secion of &lt;sectionGroup name=&#8221;system.web.extensions&#8221;&gt; that you<br />
pasted just now. Leave the other sections group untouched</p>
<p>Surround the following nodes with this</p>
<pre>&lt;location path="." inheritInChildApplications="false"&gt;&lt;/location&gt;</pre>
<pre>&lt;microsoft.sharepoint.client&gt;
&lt;SharePoint&gt;
&lt;system.web&gt;</pre>
<p>This will let the child web app to use it&#8217;s own settings</p>
<p>Go to the child web app, change the following</p>
<pre>&lt;modules runAllManagedModulesForAllRequests="true"/&gt;</pre>
<p>TO</p>
<pre> &lt;modules runAllManagedModulesForAllRequests="true"&gt;
      &lt;remove name= "SPRequestModule"/&gt;
      &lt;remove name= "PublishingHttpModule"/&gt;
      &lt;remove name= "RSRedirectModule"/&gt;
      &lt;remove name= "StateServiceModule"/&gt;
      &lt;remove name = "SharePoint14Module"/&gt;
      &lt;add name= "Session" type="System.Web.SessionState.SessionStateModule" /&gt;
    &lt;/modules&gt;</pre>
<p>This will disable all SharePoint modules in the child web app and enable back session</p>
<p>After that do IISRest and everything should be working. But if you got error 500 or a blank page please refer to <a href="http://mvolo.com/troubleshoot-iis7-errors-like-a-pro/">this page on how to debug</a></p>
]]></content:encoded>
			<wfw:commentRss>http://patrickyong.net/2012/11/04/sharing-sharepoint-2010-and-asp-net-4-0-user-credential/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Error 404 when accessing ASP.NET Website on IIS [default.aspx]</title>
		<link>http://patrickyong.net/2012/10/05/error-404-when-accessing-asp-net-website-on-iis-default-aspx/</link>
		<comments>http://patrickyong.net/2012/10/05/error-404-when-accessing-asp-net-website-on-iis-default-aspx/#comments</comments>
		<pubDate>Fri, 05 Oct 2012 08:46:49 +0000</pubDate>
		<dc:creator>Patrick</dc:creator>
				<category><![CDATA[General .NET Stuffs]]></category>
		<category><![CDATA[ASP.NET]]></category>

		<guid isPermaLink="false">http://patrickyong.net/?p=1865</guid>
		<description><![CDATA[Error 404 means file not found, but when you access an ASP.NET page like default.aspx and your double checked its existence, all this doesn&#8217;t make sense. The next thing to look into is the DLL assemblies referenced by the web &#8230; <a href="http://patrickyong.net/2012/10/05/error-404-when-accessing-asp-net-website-on-iis-default-aspx/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>Error 404 means file not found, but when you access an ASP.NET page like default.aspx and your double checked its existence, all this doesn&#8217;t make sense. The next thing to look into is the DLL assemblies referenced by the web application. In many case the DLL is not copied into the server either in the bin folder or the General Assembly Cache</p>
]]></content:encoded>
			<wfw:commentRss>http://patrickyong.net/2012/10/05/error-404-when-accessing-asp-net-website-on-iis-default-aspx/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Notes from SharePoint 2013 Ignite Training Day 4</title>
		<link>http://patrickyong.net/2012/10/01/notes-from-sharepoint-2013-ignite-training-day-4/</link>
		<comments>http://patrickyong.net/2012/10/01/notes-from-sharepoint-2013-ignite-training-day-4/#comments</comments>
		<pubDate>Mon, 01 Oct 2012 15:23:26 +0000</pubDate>
		<dc:creator>Patrick</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://patrickyong.net/2012/10/01/notes-from-sharepoint-2013-ignite-training-day-4/</guid>
		<description><![CDATA[Disclaimer: While this training in conducted by services folks from Microsoft Corp, notes here include my own understanding and gut feel. Some observations here do not apply when SharePoint 2013 RTMs later. Office Services Both lab and my own built &#8230; <a href="http://patrickyong.net/2012/10/01/notes-from-sharepoint-2013-ignite-training-day-4/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>Disclaimer: While this training in conducted by services folks from Microsoft Corp, notes here include my own understanding and gut feel. Some observations here do not apply when SharePoint 2013 RTMs later.</p>
<h1>Office Services</h1>
<p>Both lab and my own built VM cannot start Microsoft .NET Framework 4.0 NGEN v4.0.XXXX services but the SP startup scripts will try to start this</p>
<h2>Excel Services</h2>
<p>Now you have Excel Form<br />
Excel everywhere (its like OLE but works on web page)<br />
Javascript API on your Excel sheets!!</p>
<p>&nbsp;</p>
<h2>Word Automation Services</h2>
<p>CSOM access to Word Automation Services<br />
Can convert to other format PDF and XPS<br />
Still no access to protected Word files<br />
Still does not run on hosted model (Only as Farm solution)</p>
<h2>PowerPoint Automation Services (New)</h2>
<p>Same model as Word<br />
Source from PPT and PPTX<br />
Convert to PPTX, PDF, XPS, JPG, PNG</p>
<p>Deck of multiple slides when converted to JPG and PNG will be separate files</p>
<p>Translation Services<br />
Cloud based solution using Bing<br />
Also based on WAS programming model<br />
Can translate sites and documents</p>
<p>Note: No extensibility point to use other translation engine</p>
<p>At the moment its cost free for Bing translation but Product Manager to confirm later</p>
<h1>Social</h1>
<p>Skydrive Pro is a new name of SharePoint Workspaces<br />
Community is a new feature in SP2013</p>
<p>MySite broken into Newsfeed, Sites and SkyDrive<br />
One can do microblogging now</p>
<p>My Task gives you unified view of task from various SP sites and Exchange</p>
<p>But SP and Exchange still have their own task silo<br />
So the Windows Phone still don&#8217;t automatically shows alert on SP tasks</p>
<p>The Social services make heavy use of App Fabric Cache<br />
Work Management Service Application will goes around pull task</p>
<p>Yammer the cloud enterprise social site, acquired by Microsoft<br />
SP2013 does not have integration with Yammer yet<br />
Yammer does have web part for SP2010<br />
Yammer has a rich set of JS API, there are demos later on how to integrate SP2013 Communities with Yammer Groups<br />
However Yammer may remain a on the cloud service</p>
<p>Still there is no Pool and Quiz web part</p>
<p>Community is a new Site Template</p>
<p>Badges and reputations exist in Communities</p>
<p>Social and gamification works like ring fence certain pieces of information and apply. It is not site wide.</p>
<p>For lab file use MsOnlineClaimsHelper for O365 ??</p>
<p>For Social, things like profanities filtering and site wide point system are TBD</p>
<h1>Mobile</h1>
<p>Now can stored geo code info in a new Location Field, but this has to be done via custom scenario with coding<br />
Actually its more about Windows Phone/ Windows 8 at the lab<br />
Think of Windows Azure Mobile Service</p>
<p>Supports FBA, O365, Basic authentication<br />
Cross firewall to be done via UAG or Alternative Access Mapping</p>
<p>Will Reporting Service 2012 supports FBA? I think only supports claim based but not FBA</p>
<p>For the lab VS2012 does not allow Mobile Dev in Windows Server</p>
<p>Push Notification can register Windows Phone but cross fingers for Windows 8 also</p>
<p>To activate go to Site Features &#8211;&gt; Push Notifications Support &amp; Push Notifications</p>
<p>Uses Bing Map in the phone</p>
<h1>Napa Office 365 Development Tool</h1>
<p>Available on Office 365 Preview<br />
Runs only in Developer Site Collection</p>
<p>www.napacloudapp.com</p>
<p>Still in Beta, if you click Create and nothing happens go out and do again</p>
<p>Semi Intellisense is here, for HTML and Javascript<br />
Error highlighting is here already<br />
Documentation is available<br />
There is hover over explanation<br />
Debugging not there yet, but its a planned feature<br />
Napa projects can be opened in Visual Studio without download locally<br />
From VS, source code available for TFS Preview on the cloud</p>
<p>Supports IE 9 above but also will work on other browsers. I assume its HTML5 based</p>
<h1>Theme Design</h1>
<p>How easy to change the SharePoint theme?<br />
You can drag wallpaper onto the site<br />
Change the colour scheme and font<br />
So we need to find out more<br />
1. Can we add new Site Layout and Font?<br />
2. How to change to more complex theme?</p>
<p>&nbsp;</p>
<h1>Apps for Office</h1>
<p>Build on Web Extensibility Framework, allows HTML and JS developers to build Office plugin<br />
Ends up one can target Office Web Apps as well<br />
On desktop mode, it allows Office to host the web page code via the IE Trident engine and let the code access the document<br />
Less feature than VSTO i.e. you can&#8217;t play with the chrome<br />
Some Javascript functionalities are turned off, i.e. alerts can&#8217;t run</p>
<p>Can run on Office store and also on private folder share<br />
This is known as Agave in beta</p>
<p>No drag and drop eventing for now</p>
<p>The HTML app is actually a remote web app as its a ASP.NET website<br />
You can&#8217;t do cross domain call… unless via json proxy</p>
<p>Manifest file loaded into registry<br />
CurrentUser -&gt; Microsoft -&gt; office -&gt; 15 -&gt; Wef</p>
<p>People now install apps now based on reviews… people used to choose based on system requirements</p>
<p>Can be install via Exchange App Catalog but its more of a push model, Admin install Exchange App and its visible to users</p>
<p>Do we have a offline mode?</p>
<p>Admin can disable Office Store with GPO</p>
<p>Check out telemetry services for Office<br />
You can find out the type of Office and Office Apps in the enterprise</p>
<p>SharePoint can be an App Catalog</p>
<p>When an app is added to a document, the bread crumb will change and become a GUID</p>
<p>Does not work for protected document at the moment</p>
]]></content:encoded>
			<wfw:commentRss>http://patrickyong.net/2012/10/01/notes-from-sharepoint-2013-ignite-training-day-4/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Notes from SharePoint 2013 Ignite Day 3</title>
		<link>http://patrickyong.net/2012/09/27/notes-from-sharepoint-2013-ignite-day-3/</link>
		<comments>http://patrickyong.net/2012/09/27/notes-from-sharepoint-2013-ignite-day-3/#comments</comments>
		<pubDate>Thu, 27 Sep 2012 15:18:45 +0000</pubDate>
		<dc:creator>Patrick</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://patrickyong.net/?p=1857</guid>
		<description><![CDATA[Disclaimer : Due to the pre-release nature of the product, the notes I taken might contain information that no longer be relevant upon RTM of the product. It contain both notes I taken during the class and from discussion with &#8230; <a href="http://patrickyong.net/2012/09/27/notes-from-sharepoint-2013-ignite-day-3/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>Disclaimer : Due to the pre-release nature of the product, the notes I taken might contain information that no longer be relevant upon RTM of the product. It contain both notes I taken during the class and from discussion with peers. On top of that they might contain thoughts I have when going through the hands on lab which might be inaccurate. Where its possible I put a side note that certain information require further fact finding from the reader. If you are new to SharePoint or even SharePoint 2013, I suggest you find out more first from http://dev.office.com</p>
<h2>Business Connectivity Services</h2>
<p>SharePoint Online now supports BCS</p>
<p>OData can be a Data Source to BCS</p>
<p>Used in SP Online as SP Online cannot use DLL</p>
<p>SQL Server Reporting Services can return OData result</p>
<p>*SharePoint Designer does not support OData datasource</p>
<p>There is a Northwind database exposed as OData on Azure marketplace so you can play around with it</p>
<p>http://services.odata.org/Northwind/Northwind.svc</p>
<p>External Content Type is Farm level in 2010, now is App level</p>
<p>We now have Event Receivers in BCS,</p>
<p>Example data changed in SQL Server data source, BCS will be notified. It will be captured by the event receiver</p>
<p>Have to investigate what are available in SP Foundation</p>
<p>User permission setting has to be done one by one even people picker allows you to choose more than one user</p>
<h2>ECM</h2>
<p>ECM improvement is around eDiscovery and Taxonomy</p>
<p>Goal to achieve to full DoD certification</p>
<p>eDiscovery improves upon Record Management in 2007/ 2010</p>
<p>eDiscovery mainly applies to companies with HQ or office in US</p>
<p>ECM big bet also include Exchange where mailbox can be a content source. Retention and compliance can be apply on mail</p>
<p>Acquire &#8211; Attain &#8211; Expose</p>
<p>Clearwell which is just acquired by Symantec [find out more]</p>
<p>Its about empowering legal teams</p>
<p>Centralize management can cover Lync, SharePoint and Exchange. Lync is here because achieving is sent to Exchange</p>
<p>Exchange and SharePoint to share the same search platform</p>
<p>There is a new Site Template called Discovery Set this is a case management site template</p>
<p>ECM comes to SharePoint Online</p>
<p>Also new in 2013 is the Site Mailbox container… email&#8217;s attachments are stored in SharePoint. For secured email [IRM'ed] and encrypted emails might not be supported. TBD</p>
<p>IRM&#8217;ed email has something to do with CSP…. and the key is tied to the workstation. How does SP access these?</p>
<p>One Note can comes in as Document Set. CSOM can access Document Set</p>
<p>Content Management Interoperability Services Connector comes OOB</p>
<p>In the lab, Ken Shansez does not exist, use Ken Ewerd instead</p>
<p>Limit of 30k terms in terms set and 1mil in total back in 2010</p>
<h2>Search</h2>
<p>FAST and SharePoint Search becomes a single extensible platform</p>
<p>It&#8217;s FAST Engine + SharePoint Crawler</p>
<p>The same Search platform works on Exchange</p>
<p>New search capabilities</p>
<ul>
<li>Topic Pages</li>
<li>Content by Search</li>
<li>My Task (Pro)</li>
</ul>
<p>Plugins from customers and partners</p>
<p>Crawl is now separated from the Content Pipeline</p>
<p>Protocol handler replaces iFilter but certain protocol handler still maps back to existing iFilter</p>
<p>Index storage is now on DB, where FAST used to store in disk</p>
<p>On Search federation we have Federated Result Source</p>
<p>A lot of the architecture questions are answered in IT Pro sessions</p>
<p>FAST Query Language still supported</p>
<p>SQL Query has been removed</p>
<p>Keyword query is preferred</p>
<p>Queries can be REST based</p>
<p>Settings can be exported to different environment for Dev to Prod setup</p>
<p>Another new concept know as Search Vertical</p>
<p>No-code customisation</p>
<ul>
<li>Result Sources : Federated location. Can be Local and remote SP index (Can use SSO ID), OpenSearch [Bing], or Exchange [I wonder if Lucene is supported]. Site Collection admin can now change the scope in their own sites</li>
<li>Query Rules : Allow customisation of returned results. You can affect rank as in FAST</li>
<li>Result Types : How to display results. Replaces XSLT to render results</li>
<li>SPNavigator : replace the tabs in Search Center of 2010</li>
</ul>
<p>To disable search security trim, you just configure a result source acting as a different user credential</p>
<p>PDF support is now OOB</p>
<p>Some file type filters from FAST are not available in 2013&#8230;</p>
<p>How to do medical search result? in FAST you ca build alias and dictionary. Not seen in 2013</p>
<h2>Web Content Management</h2>
<p>No more variations… just channels</p>
<p>For multi lingual, you can use translation services or use XLIFF file format for manual translation</p>
<p>Navigation is now term store based… you have to reindex the site when you progress to a new level. Else you won&#8217;t need it on the page. However the 7 level limitation might still be there… need to investigate</p>
]]></content:encoded>
			<wfw:commentRss>http://patrickyong.net/2012/09/27/notes-from-sharepoint-2013-ignite-day-3/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Notes from SharePoint 2013 Ignite Day 2</title>
		<link>http://patrickyong.net/2012/09/27/notes-from-sharepoint-2013-ignite-day-2/</link>
		<comments>http://patrickyong.net/2012/09/27/notes-from-sharepoint-2013-ignite-day-2/#comments</comments>
		<pubDate>Wed, 26 Sep 2012 16:48:20 +0000</pubDate>
		<dc:creator>Patrick</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://patrickyong.net/?p=1853</guid>
		<description><![CDATA[Disclaimer : Due to the pre-release nature of the product, the notes I taken might contain information that no longer be relevant upon RTM of the product. It contain both notes I taken during the class and from discussion with &#8230; <a href="http://patrickyong.net/2012/09/27/notes-from-sharepoint-2013-ignite-day-2/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>Disclaimer : Due to the pre-release nature of the product, the notes I taken might contain information that no longer be relevant upon RTM of the product. It contain both notes I taken during the class and from discussion with peers. On top of that they might contain thoughts I have when going through the hands on lab which might be inaccurate. Where its possible I put a side note that certain information require further fact finding from the reader. If you are new to SharePoint or even SharePoint 2013, I suggest you find out more first from http://dev.office.com</p>
<h2>Client Side Object Model (CSOM)</h2>
<p>&nbsp;</p>
<p>Still _vti_bin/client.svc but supports REST interface now</p>
<p>Very impossible to write own REST access in 2010</p>
<p>REST implemented in ODATA</p>
<p>New functions added to access host of stuff esp Workflow, Business Data, and user Profiles</p>
<p>Can also be access from _api for REST</p>
<p>&nbsp;</p>
<p>ListData.svc still around for backward compatibility but you don&#8217;t have above new features. Going forward should stop using ListData.svc</p>
<p>More explanation about the new features at dev.office.com</p>
<p>&nbsp;</p>
<p>ODATA Tips and Tricks</p>
<p>Just communicate using HttpWebRequest and HttpWebResponse</p>
<p>One can query the result using XDocument.Descendants</p>
<p>&nbsp;</p>
<p>For JSON response, result always wrapped in the &#8220;d&#8221; outer object</p>
<p>This is to prevent replay attached or embedded method calls</p>
<p>&nbsp;</p>
<p>JsRender is a good library to access the JSON data</p>
<p>&nbsp;</p>
<p>FormDigest has to be provided for put and post method. Need to investigate more</p>
<p>&nbsp;</p>
<p>To access fields, use the Display Name for REST API</p>
<p>&nbsp;</p>
<h2>OAuth and Authentication</h2>
<p>&nbsp;</p>
<p>Problems in SP2010</p>
<p>RunWithElevatedPriveleges runs as sharepoint\System or revert to Windows identity of host app pool</p>
<p>You may access information that user not permitted to see</p>
<p>&nbsp;</p>
<p>However Sandboxed always run as current logged in user</p>
<p>&nbsp;</p>
<p>SharePoint 2010 solution only supports user authentication not authorization</p>
<p>&nbsp;</p>
<p>In 2013</p>
<p>Apps are now given first class identities, we dont give them user ID and password</p>
<p>In 2013, you have to configure permission for apps</p>
<p>&nbsp;</p>
<p>In 2013 everything is claim by default</p>
<p>&nbsp;</p>
<p>Between sp2013 and app, token is provided in Oauth</p>
<p>&nbsp;</p>
<p>Steve Pascal writes a lot about claims in SP</p>
<p>&nbsp;</p>
<p>Every SP installation has one tenant, look at the DB; user profile there is a guid refer to the tenancy</p>
<p>&nbsp;</p>
<p>There is a ID stamping on user profile to separate data from tenants</p>
<p>&nbsp;</p>
<p>Spence Harbor writes a lot about multi tenancy</p>
<p>&nbsp;</p>
<p>Multi tenancy is not recommended for on premise installation of SP, built for O365</p>
<p>&nbsp;</p>
<p>While you grant permission for app, it is all or nothing permission for specific scope</p>
<p>Default permission is read, you can request for more inside your app manifest</p>
<p>There is no item level permission for apps</p>
<p>During deployment, user will be notified of the rights request and grant consent to the app</p>
<p>&nbsp;</p>
<p>Permission granted on content type… it will be inclusive [Got to investigate to confirm]</p>
<p>&nbsp;</p>
<p>STS is secured token service, and ACS acts as one</p>
<p>in 2013 Windows Azure ACS acts as authentication server</p>
<p>ACS lives on cloud, and is there charges to use ACS?</p>
<p>&nbsp;</p>
<p>Does that mean we need Internet access? Is there a on premise solution?</p>
<p>&nbsp;</p>
<p>http://siteaddress/_layouts/15/appregnew.aspx but will be taken out in future. Have to use PowerShell instead</p>
<p>&nbsp;</p>
<p>OAuth must be done in SSL to prevent replay and disable access to info passed on wire</p>
<p>&nbsp;</p>
<p>Context token is per session, OAuth token is long live</p>
<p>&nbsp;</p>
<p>The authentication workflow</p>
<p>1. Client &#8211; Request &#8211; SP</p>
<p>2. SP &#8211; Request Context Token &#8211; ACS</p>
<p>3. ACS &#8211; Signed ContextToken - SP</p>
<p>4. SP &#8211; Page -IFrame &#8211; Client</p>
<p>5. Client &#8211; Request IFRAME &#8211; App [The request contains the Context Token]</p>
<p>6. App &#8211; request token &#8211; ACS</p>
<p>7. ACS &#8211; Access Token &#8211; App [The access token belongs to the user and has specific rights]</p>
<p>8. App &#8211; Request and Access Token &#8211; SP [Access Token is stored in httpwebrequest header]</p>
<p>9. SP &#8211; data &#8211; App</p>
<p>10. App &#8211; iframe content &#8211; Client</p>
<p>&nbsp;</p>
<p>Server to Server Trust (S2S)</p>
<p>On premise farms request explicit configuration. Alternative will be to create a high trust app and skip OAuth. Do this when you can&#8217;t access ACS.</p>
<p>&nbsp;</p>
<p>Slide 35 is obsolete</p>
<p>&nbsp;</p>
<p>You might want to disable SSL on dev machine using Powershell</p>
<p>&nbsp;</p>
<p>$service = Get-SPSecurityTokenServiceConfig()</p>
<p>$service,AllowOAuthOveHttp = True</p>
<p>&nbsp;</p>
<p>FBA access is TBD</p>
<p>&nbsp;</p>
<p>For hands on go to http://dev.office.com… under Authorisation and Authentication look for  How to create high-trust apps for SP2013 using the server to server protocol (Advanced Topic)</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<h2>Remote Event Receiver</h2>
<p>SharePoint got to act as a data hub</p>
<p>SharePoint event receiver can now talk to external system</p>
<p>But don&#8217;t use this for geo replication or mirroring or sync.</p>
<p>BCS will have event receiver</p>
<p>External Web service can call back SharePoint via token from ACS</p>
<p>No guarantee delivery, non transactional</p>
<p>&nbsp;</p>
<p>Tips:</p>
<p>In debugging after VS deploy the WCF app, the secondary web app symbol might not be loaded. To force loading, use Debug &#8211;&gt; Start new instance</p>
<p>&nbsp;</p>
<h2>Workflow</h2>
<p>&nbsp;</p>
<p>On 2013, workflow is now a service outside of SharePoint.</p>
<p>Moved to Windows Azure Workflow, however it is available for on-premise deployment</p>
<p>Now is WF4.0 based, which has better</p>
<p>-Modelling</p>
<p>-Scale</p>
<p>-Tracking</p>
<p>&nbsp;</p>
<p>For SharePoint, there is REST API and communicate via OAuth</p>
<p>&nbsp;</p>
<p>However SP2010 workflow still runs in SP2013. Continue to be hosted by SP under .NET 3.5</p>
<p>&nbsp;</p>
<p>Windows Azure Workflow is not exactly a Cloud product like SQL Azure</p>
<p>You can now run Windows Azure Workflow on a separate machine out of the SP Farm</p>
<p>&nbsp;</p>
<p>Thinking out loud, is it possible to have my own Workflow engine implementation?</p>
<p>&nbsp;</p>
<p>WF 3.5 has some serialisation problem</p>
<p>&nbsp;</p>
<p>SP 2013 has a new Stage concept but its not similar to State Workflow because the lack of eventing model</p>
<p>&nbsp;</p>
<p>SP Designer can now call REST/ SOAP web services</p>
<p>It can also call SP SPI, query DB, Consume feeds</p>
<p>&nbsp;</p>
<p>Now in SP Designer, you can switch between designer &amp; sentence style</p>
<p>&nbsp;</p>
<p>The lab VM cannot switch user in SP Designer, we have to test it in own build VM</p>
<p>The lab VM also cannot export to Visio. No error message appears</p>
<p>&nbsp;</p>
<p>Visual designer runs inside SP Designer but requires that Visio to be installed</p>
<p>&nbsp;</p>
<p>Underneath, Stage is actually Flow Step in WF 4.0</p>
<p>In 2013 you can&#8217;t associate Task Form directly via SP Designer, reason being Infopath 2013 does not support the Apps Model</p>
<p>Going forward the recommended practice is to create a HTML form</p>
<p>&nbsp;</p>
<p>Note on InfoPath 2013</p>
<p>InfoPath 2013 is not being deprecated, but is so more about doing list customisation, offline form and digital signature</p>
<p>Its a play on the XForm, try to stay away from doing code behind for InfoPath 2013</p>
<p>But for developers, look into the new Apps Model with HTML based form</p>
<p>Also consider Access Services 2013 to build good online forms, especially for powerful</p>
<p>Still InfoPath investment developers have in SP2010 it will run in 2013</p>
<p>Also Access 2013 can do almost what LightSwitch can do.</p>
<p>&nbsp;</p>
<p>Custom Activity in SP2010/ 2007 cannot be imported for use with SP2013 workflows</p>
<p>But one can look into the Workflow Interop Bridge</p>
<p>&nbsp;</p>
<p>WF4.0 workflow for SharePoint is actually declarative. @_@</p>
<p>Custom code should live inside individual web services</p>
<p>There is no custom code activity now</p>
<p>&nbsp;</p>
<p>Programmatic workflow can only be created as pure Windows Azure Workflow instance</p>
<p>&nbsp;</p>
<p>Direction of workflow as middle tier app for Apps for SP and Apps for Office</p>
<p>Use them for</p>
<p>Model how people work</p>
<p>Automate monitor and improve business process</p>
<p>Connect and integrate with other system</p>
<p>&nbsp;</p>
<p>Now WF 4.0 has a tracking DB, which also used by SP2013, you can build analytics around this database</p>
<p>You can now don&#8217;t depends on the Workflow History table already</p>
<p>&nbsp;</p>
<p>Cool stuff with Stage in SP2013 WF, you can have evaluation on Stage 1, check for &#8216;bread crumbs&#8217; and rearrange how the WF will run.</p>
<p>&nbsp;</p>
<p>In the lab, administrator or system account cannot start workflow instance</p>
<p>&nbsp;</p>
<p>Also notice that you can&#8217;t sign in as another user already</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://patrickyong.net/2012/09/27/notes-from-sharepoint-2013-ignite-day-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Notes from SharePoint 2013 Ignite Day 1</title>
		<link>http://patrickyong.net/2012/09/26/notes-from-sharepoint-2013-ignite-day-1/</link>
		<comments>http://patrickyong.net/2012/09/26/notes-from-sharepoint-2013-ignite-day-1/#comments</comments>
		<pubDate>Tue, 25 Sep 2012 16:41:56 +0000</pubDate>
		<dc:creator>Patrick</dc:creator>
				<category><![CDATA[Sharepoint]]></category>
		<category><![CDATA[sharepoint2013]]></category>

		<guid isPermaLink="false">http://patrickyong.net/?p=1849</guid>
		<description><![CDATA[Disclaimer : Due to the pre-release nature of the product, the notes I taken might contain information that no longer be relevant upon RTM of the product. It contain both notes I taken during the class and from discussion with &#8230; <a href="http://patrickyong.net/2012/09/26/notes-from-sharepoint-2013-ignite-day-1/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>Disclaimer : Due to the pre-release nature of the product, the notes I taken might contain information that no longer be relevant upon RTM of the product. It contain both notes I taken during the class and from discussion with peers. On top of that they might contain thoughts I have when going through the hands on lab which might be inaccurate. Where its possible I put a side note that certain information demands further fact finding from the reader. If you are new to SharePoint or even SharePoint 2013, I suggest you find out more first from http://dev.office.com</p>
<h2>Apps for SharePoint Model</h2>
<p>With Farm Solution,</p>
<p>We have &#8216;BIG&#8217; server touches, meaning there are</p>
<div>     App Pool recycles</div>
<div>     Hard to roll back esp if you didn&#8217;t version your solution</div>
<div>     Outage is a pain</div>
<div>With farm solution SharePoint is an application platform, now SharePoint looks like a service bus endpoint with Apps</div>
<div>Apps for SharePoint can be compared to Facebook Apps in a sense both use OAuth to authenticate themselves against the platform</div>
<div>Fabulous 40 template gives you an idea what apps can be build.</div>
<div>In terms of performance, the new Apps model will have network latency issue. It is a slide trade off to gain better CPU usages on SharePoint Farm as most SP performance problem comes from on server solutions</div>
<div>With Apps for SharePoint project template, developers can create a project without SharePoint installed locally</div>
<div>Because apps live on a separate domain, do not configure apps to be on the corporate sub domain such as apps.yourcompany.com</div>
<div>Reason being while IE doesn&#8217;t allow websites to access cookies on parent and other sub domain such as other.youngcompany.com, other competing browser does.</div>
<div>Very danger when enterprise has apps from different vendor which try to do something to their competitor</div>
<div>This open up probability of cookie poisoning so try to use something like yourapps.com</div>
<div>Another thing to investigate is SSL Wildcards [Need to study more on this]</div>
<div>In 2013, OAuth will be a learning curve.</div>
<div>OAuth is not a sign in mechanism, only for Apps to authenticate on SharePoint</div>
<div>Going forward authentication defaulted to Claim based and not NTLM. What works for NTLM now works on Claims, its a total flip over.</div>
<div>But Sandboxed solution is still relevant for branding apps i.e. custom Master Page.</div>
<div>Strategy going forward to start with Apps, and use Solution when necessary</div>
<div>Sandboxed solution is deprecated in SP2010, means future might not support.</div>
<div>But the sandboxed APIs are not marked as [absolute] in .NET, because Sandboxed APIs use the same library as in farm solution. Difference is just they have different CAS policy</div>
<div>Only advantage Solutions has now is the ability to be pushed out to site collections. Apps maintain a pull approach initiated by users</div>
<div>There has been advice to create Content Type programmatically because declarative Content Type [XML] will not upgrade the list in new solution version deployment</div>
<div>Now the reverse applies</div>
<div>Not known to many WSP deployment has local only mode, which is used by VS. meaning it is not pushes to every servers on the farm.</div>
<div>There is no changes to WSP development in 2013</div>
<div>Apps for SharePoint has a App Web container. It&#8217;s like another SPWeb but do not create Farm solution to manipulate the App Web</div>
<div>Farm Solution in 2013 is not in Full Trust. Some of the reasons</div>
<div>caspol.exe not around now in Windows server to change the site CAS policy</div>
<div>.NET 4.0 above does not use CAS by default</div>
<div>Since Apps for SharePoint live in another site physically, during debugging VS will modify the local host file</div>
<div>Apps for SharePoint only works with Windows claim at the moment. FBA support TBD</div>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://patrickyong.net/2012/09/26/notes-from-sharepoint-2013-ignite-day-1/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
