{"loaderData":{"0-8":{"posts":[{"id":20,"slug":"creating-and-deploying-vsto-documents-inside-sharepoint-document-libraries","title":"Creating and deploying VSTO Documents inside SharePoint Document Libraries","content":"

This is a repost of an article that was lost due to a server crash.

Visual Studio Tools for Office (VSTO) Documents can be deployed to or utilized as templates for a SharePoint Document Library. The process to develop VSTO Documents, deploy them to the SharePoint server, and set the proper security policies on the client machine in order for the documents to run properly can be easily repeated once you understand all the pieces of the puzzle.

I have not been able to find complete documentation for this process on the Internet to date. I have found several web pages that provide pieces of the puzzle, but no comprehensive solution. I discussed this architecture with some Microsoft TS’s and they liked the architecture and approach and gave it two thumbs up.

VSTO Document Basics

To begin, it is important to understand how the VSTO Documents, the SharePoint server, and the target client machines interact.

The following diagram helps illustrate the architecture:

$\"\"$

VSTO Documents contain a Deployment Manifest. Inside the Document’s Deployment Manifest, the location of the Assembly the VSTO Document relies upon is stored. This Deployment Manifest can be modified programmatically to point to any location where the Assembly the Document relies upon is stored. By default the Deployment Manifest specifies that the Assembly the document relies upon is stored in the same directory as the Document.

The VSTO Document’s Assembly can be deployed to any file share the user who opens the VSTO document has access to. This location can be on a stand alone file server, or even a file share on the SharePoint server itself. The VSTO Document’s Assembly is a .dll file.

In order for the client machine to properly load and render the VSTO Document and related Assembly, the client machine needs to trust the location from which the VSTO Document is opened and the location from which the Assembly is opened. Creating Security Policies on the client machine that trust the location from which the VSTO Document is opened allows the VSTO Document to properly load and render.

Scenario

The following scenario will be used as an example to demonstrate how to develop, configure and deploy a VSTO Document that will be used as a template for a SharePoint Document Library. Terms that appear in parenthesis are used to represent the various components of the solution and maintain consistency throughout the instructions.

An existing Word Document Template (Sample.dot) utilizes Macros to fill data in the Word Document Template. The majority of the data the users enter into the Macros to fill the document exists within a database, however users are presently keying the information into the Macro prompts manually. The document needs to be migrated to the VSTO format (VSTOSample.dot) in order to take advantage of the data in the database to expedite document creation.

Once the existing Word Document Template has been converted to the VSTO format the VSTO Document Template should be deployed as a template for a given document library (Sample Document Library) on the SharePoint Server (SampleSharePointServer).

Users must be able to open the VSTO Document Template from the Sample Document Library on the SampleSharePointServer and create a new Word Document from the VSTO Document Template. The new Word Document should be able to be saved to the Sample Document Library.

Prerequisites

This solution utilizes the following technologies:

Development environment:

Microsoft Office SharePoint Server 2007 (MOSS 2007)

Visual Studio .NET 2005

Visual Studio Tools for Office 2005 (VSTO 2005)

Client Machine:

Please see the following web page on the MSDN for client machine prerequisites and instructions for installing the prerequisites:

http://msdn2.microsoft.com/en-us/library/2ac08ee2(VS.80).aspx

The Solution

To successfully implement the aforementioned scenario several tasks need to be done.

These tasks are as follows:

Convert the existing Word Document Template (Sample.dot) to the VSTO format (VSTOSample.dot).
Create a share on a stand alone file server or the SampleSharePointServer server (This example uses a file share on the SampleSharePointServer.)
Edit the VSTO Document Deployment Manifest to point to the file share where the VSTO Document’s Assembly is stored.
Create a new Sample Document Library Feature in SharePoint for the document library that will utilize the VSTO Document Template. (Please see the Creating a Custom Document Library Feature in WSS V3 / MOSS 2007 article for instructions.)
Install the Sample Document Library Feature on the SampleSharePointServer. (Please see the Creating a Custom Document Library Feature in WSS V3 / MOSS 2007 article for instructions.)
Register the Sample Document Library Feature on the site definition you want the Sample Document Library to be created on when a new SharePoint site is created based on that site definition. (Please see the Adding a Document Library Feature to a Site Definition in WSS V3 / MOSS 2007 article for instructions.)
Deploy the VSTOSample.dot file to the SampleSharePointServer.
Deploy the VSTOSample.dll to the file share on the SampleSharePointServer.
Create Security Policies on the client machine that trust the location the VSTOSample.dot file will be opened from.
Test and rejoice!

Step 1: Convert the existing Word Document Template (Sample.dot) to the VSTO format (VSTOSample.dot)

To convert an existing Word Document Template (Sample.dot) to the VSTO format follow these steps:

Open Visual Studio .NET 2005.

Click File | New | Project.

Under Visual C# | Office, select Word Template.

Name the Project VSTOSample.

Click OK.

Select Copy an existing document. (Sample.dot)

Click OK.

At this point VS.NET 2005 converts the existing Sample.dot file to the VSTO format.

Rename Sample.dot in the VS.NET IDE to VSTOSample.dot.

*Note: This can also be done for Word Documents, Excel Workbooks and Excel Templates.

Select Word Document during project creation to convert a .doc file to the VSTO format.

Select Excel Workbook during project creation to convert a .xls file to the VSTO format.

Select Excel Template during project creation to convert a .xlt file to the VSTO format.

*Note: If you are not converting an existing Document follow the same steps as above except select Create a new document instead of Copy an existing document when the dialogue with these options appears during project creation.

Build the project.

Now let’s put some code into the document that will let us know the document was able to access the Assembly and execute code from it after we have deployed the document.

Open the ThisDocument.cs file in the VSTOSample project in the VS.NET 2005 IDE.

Add the following code to the ThisDocument_Startup method.

MessageBox.Show(\"I'd rather be skiing!\");

Run the project. When the project runs the document will appear, then a textbox will appear with the message “I’d rather be skiing!”.

Click OK on the message box and close the document.

Let’s add some more code to the document to demonstrate how a VSTO document can be more efficient at populating documents with information compared to Macros.

First we will add an ActionsPane to the VSTO Document so we have a place to put some simple controls.

In the Visual Studio .NET 2005 IDE right click the VSTOSample project.

Click Add | New Item

Select Actions Pane Control

Name the control ActionsPane.cs

Click Add

Return to the ThisDocument.cs file in the VSTOSample project in the VS.NET 2005 IDE.

Add the following code at the class level:

Private ActionPane actionPane = new ActionPane();

Add the following code to the ThisDocument_Startup method:

this.ActionsPane.Controls.Add(actionPane);

Run the project. When the project runs the document will appear, then a textbox will appear with the message “I’d rather be skiing!” After you click the OK button the Document Actions Pane will appear on the right side of the VSTO Document.

Close the document.

Now let’s add some controls to the Actions Pane.

Open the ActionPane in design mode in VS.NET 2005.

Drag a ComboBox Control and drop it on the ActionsPane designer surface.

Name the ComboBox resortsComboBox

Right click the resortsComboBox control and select Properties

In the Properties Pane scroll to the Items Property and click the … button

Add the following items to the collection of items:

Arapahoe Basin

Wolf Creek Ski Area

Vail

Telluride

Steamboat

Alta

Now, let’s add a control to the document to display our favorite ski resort.

Open the VSTOSample.dot file in the VSTOSample project in design mode.

Add in a BookMark control to the ToolBox in the VS.NET 2005 IDE.

Right click on the ToolBox in the VS.NET 2005 IDE.

Click Choose Items…

Sort by Namespace

Select all the items in the Microsoft.Office.Tools.Word namespace.

Click OK

Type the words “My favorite ski resort is: “ into the document.

Drag a BookMark Control into the document and drop it at the end of the line you just typed.

Name the control favoriteSkiResortBookMark

Finally, let’s add an event handler to the resortsComboBox control to populate the document with the ski resort selected in the resortsComboBox.

Click the button to display the Event Handlers for the resortsComboBox control.

Double click in the SelectedIndexChanged event to create the event handler.

Open the ActionPane.cs file in code view.

Add the following code to the resortsComboBox_SelectedIndexChanged event handler method:

Globals.ThisDocument.favoriteSkiResortBookMark.Text = resortsComboBox.Text;

Run the project. Just like last time, when the project runs the document will appear, then a textbox will appear with the message “I’d rather be skiing!” After you click the OK button the Document Actions Pane will appear on the right side of the VSTO Document. The resortsComboBox control will be populated with the ski resorts you enetered. Selecting an item in the resortsComboBox will populate the document with the name of the selected ski resort in the location where you placed the favoriteSkiResortBookMark control.

Close the VSTOSample project.

*Note: This is a very simple demonstration that illustrates the power of VSTO Documents. Although the data in this example (The Ski Resort Names) does not come from a database, you can easily utilize the power of ADO.NET to return information from a database to populate data bound controls in the Actions Pane. Web Service calls may be used to retrieve the data from back end data sources, so your documents remain loosely coupled to your data layer.

Step 2: Create a share on a stand alone file server or the SampleSharePointServer server (This example uses a file share on the SampleSharePointServer.)

I’m going to assume you know how to do this. For example’s sake I’ll call this share: VSTODocs

Step 3: Edit the VSTO Document Deployment Manifest to point to the file share where the VSTO Document’s Assembly is stored.

I’ve taken care of wrapping the code that does this inside a handy little Windows Form Application that will do this for you. The VSTO Document Deployment Manifest Editor application allows you to easily edit the VSTO Document Deployment Manifest to point to the location where you will deploy the Assembly for the VSTO Document.

Here is a screenshot of the application:

$\"\"$

To edit the VSTO Document’s Deployment Manifest simply click the Browse button and browse to the location of the VSTOSample.dot file then select it.

Then type in the UNC path for the file share you created in Step 2. (Make sure you type in the name of the .dll at the end of the path!)

Click the Edit Document Deployment Manifest button and you are done.

There is hardly any code under the hood here that actually edits the Document’s Deployment Manifest. I found the code to do this on the MSDN.

Here is the link to the page on the MSDN that has the code:

http://msdn2.microsoft.com/en-us/library/kck1ffhz(VS.80).aspx

Step 4: Create a new Sample Document Library Feature in SharePoint for the document library that will utilize the VSTO Document Template. (Please see the Creating a Custom Document Library Feature in WSS V3 / MOSS 2007 article for instructions.)

Step 5: Install the Sample Document Library Feature on the SampleSharePointServer. (Please see the Creating a Custom Document Library Feature in WSS V3 / MOSS 2007 article for instructions.)

Step 6: Register the Sample Document Library Feature on the site definition you want the Sample Document Library to be created on when a new SharePoint site is created based on that site definition. (Please see the Adding a Document Library Feature to a Site Definition in WSS V3 / MOSS 2007 article for instructions.)

These steps can be skipped if you do not want to make the document a template in a SharePoint Document Library. If you don’t want to make the document a template in a SharePoint Document Library and merely wish to upload the document to a SharePoint Document Library then proceed.

If you want to make the document a template in a SharePoint Document Library by using a SharePoint Feature please see the Creating a Custom Document Library Feature in WSS V3 / MOSS 2007 article for instructions.

Step 7: Deploy the VSTOSample.dot file to the SampleSharePointServer.

If you chose to perform steps 4, 5 and 6 then this task will already be accomplished.

If you chose not to perform steps 4, 5 and 6 then create a new SharePoint Site.

For examples sake create a site at the following location:

http://SampleSharePointServe/SiteDirectory/VSTOSample

Create a Document Library in the new VSTOSample SharePoint Site you created. Name the Document Library ‘Sample Document Library’. Upload the VSTOSample.dot file to the new Document Library you just created.

Step 8: Deploy the VSTOSample.dll to the file share on the SampleSharePointServer.

Copy the VSTOSample.dll file to the VSTODocs file share on the SampleSharePointServer.

Step 9: Create Security Policies on the client machine that trust the location the VSTOSample.dot file will be opened from.

The following commands are executed on the command line on the client machine.

These commands set up the necessary Security Policies on the client machine that specify the client trusts the location from which the VSTO Document was opened and the location where the Assembly is stored.

%windir%Microsoft.NETFrameworkv2.0.50727caspol -m -ag LocalIntranet_Zone -url \"\\SampleSharePointServervstodocs*\" FullTrust -n \"VSTO Documents\"

%windir%Microsoft.NETFrameworkv2.0.50727caspol -m -ag LocalIntranet_Zone -url \"http://SampleSharePointServer/sitedirectory/*\" FullTrust -n \"VSTO SharePoint Documents\"

You’ll notice in both commands I use a wildcard in the paths. This allows me to trust all the documents and assemblies that are opened from these locations. In a development environment this is a nice approach to take because security is not a big consideration. However, in a production environment I recommend changing these paths to point to the particular VSTO Document and related Assembly.

These commands came from the following MSDN article:

http://msdn2.microsoft.com/en-us/library/ms404837(VS.80).aspx

*Note: To reset Security Policies to their default configuration run the following command at the command line on the client:

%windir%Microsoft.NETFrameworkv2.0.50727caspol -m -rs

Step 10: Test and rejoice!

Open Internet Explorer on the client machine.

Navigate to the VSTOSample SharePoint Site you created.

Look at the bottom toolbar of Internet Explorer.

Check to see the site is in the Local Intranet Zone. (We set the security policies on the Local Intranet Zone, so the paths we set as trusted apply to web sites opened in the Local Intranet Zone.)

Open the Sample Document Library.

Open the VSTOSample.dot file.

The VSTO Word Document Template should open and the “I’d rather be skiing!” Message Box should appear. The resortsComboBox should be populated with data, and selecting a resort will populate the document with the selected ski resort.

If this functionality works you have successfully deployed the VSTO Document to the SharePoint Document Library!

Save the VSTOSample VSTO Word Document Template to the Sample Documents Library by clicking File | Save.

Name the new file VSTOSample – Success.

Return to Internet Explorer and refresh the Sample Document Library page.

You will see you now have a Word Document named VSTOSample – Success.doc in the Sample Document Library.

Nice job! You just made a VSTO document and integrated it with MOSS 2007!

","excerpt":"","date":"2007-08-17T03:27:00","modified":"2013-07-01T20:06:22","author":"Todd Baginski","authorSlug":"todd","categories":[{"id":88,"name":"Office","slug":"office","count":21},{"id":97,"name":"SharePoint","slug":"sharepoint","count":58},{"id":84,"name":"SharePoint 2007","slug":"sharepoint-2007","count":22}],"tags":[{"id":10,"name":"Custom Development","slug":"custom-development","count":87},{"id":5,"name":"Helpful Code","slug":"helpful-code","count":70},{"id":6,"name":"HOW TO: SharePoint","slug":"how-to-sharepoint","count":31},{"id":7,"name":"SharePoint","slug":"sharepoint","count":85}],"status":"publish"}],"total":21,"totalPages":3,"currentPage":3,"archiveType":"category","archiveName":"Office","archiveSlug":"office","archivePathSegments":"office","categories":[{"id":146,"name":"AI","slug":"ai","count":1},{"id":90,"name":"Blog","slug":"blog","count":2},{"id":103,"name":"Cloud","slug":"cloud","count":68},{"id":102,"name":"Community","slug":"community","count":41},{"id":110,"name":"GitHub","slug":"github","count":4},{"id":139,"name":"Lacrosse","slug":"lacrosse","count":1},{"id":96,"name":"Mobile","slug":"mobile","count":62},{"id":46,"name":"Most Popular","slug":"most-popular","count":19},{"id":88,"name":"Office","slug":"office","count":21},{"id":104,"name":"Office 365","slug":"office-365","count":80},{"id":89,"name":"Operations","slug":"operations","count":13},{"id":121,"name":"PowerApps","slug":"powerapps","count":57},{"id":87,"name":"Publications","slug":"publications","count":17},{"id":97,"name":"SharePoint","slug":"sharepoint","count":58},{"id":84,"name":"SharePoint 2007","slug":"sharepoint-2007","count":22},{"id":98,"name":"SharePoint 2010","slug":"sharepoint-2010","count":40},{"id":99,"name":"SharePoint 2013","slug":"sharepoint-2013","count":20},{"id":106,"name":"SharePoint 2016","slug":"sharepoint-2016","count":6},{"id":118,"name":"SharePoint Framework","slug":"sharepoint-framework","count":1},{"id":83,"name":"Speaking Engagements","slug":"speaking-engagements","count":41},{"id":119,"name":"SPFx","slug":"spfx","count":1},{"id":85,"name":"SPS Events Mobile","slug":"sps-events-mobile","count":4},{"id":116,"name":"Teams","slug":"teams","count":3},{"id":1,"name":"Uncategorized","slug":"uncategorized","count":3},{"id":86,"name":"Windows 8","slug":"windows-8","count":7},{"id":101,"name":"Azure","slug":"azure","count":24},{"id":100,"name":"BCS","slug":"bcs","count":26},{"id":132,"name":"CDS","slug":"cds","count":3},{"id":120,"name":"Flow","slug":"flow","count":18}],"tags":[{"id":10,"name":"Custom Development","slug":"custom-development","count":87},{"id":7,"name":"SharePoint","slug":"sharepoint","count":85},{"id":5,"name":"Helpful Code","slug":"helpful-code","count":70},{"id":54,"name":"Mobile","slug":"mobile","count":66},{"id":45,"name":"O365","slug":"o365","count":65},{"id":112,"name":"PowerApps","slug":"powerapps","count":56},{"id":42,"name":"Cloud","slug":"cloud","count":46},{"id":122,"name":"HOW TO: PowerApps","slug":"how-to-powerapps","count":38},{"id":26,"name":"SharePoint 2010","slug":"sharepoint-2010","count":32},{"id":6,"name":"HOW TO: SharePoint","slug":"how-to-sharepoint","count":31},{"id":57,"name":"Mobility","slug":"mobility","count":28},{"id":3,"name":"Conferences","slug":"conferences","count":27},{"id":41,"name":"Azure","slug":"azure","count":21},{"id":4,"name":"BDC","slug":"bdc","count":20},{"id":40,"name":"Windows Phone 7","slug":"windows-phone-7","count":17},{"id":58,"name":"Android","slug":"android","count":14},{"id":60,"name":"iPad","slug":"ipad","count":14},{"id":68,"name":"SharePoint 2013","slug":"sharepoint-2013","count":14},{"id":23,"name":"Conference Materials","slug":"conference-materials","count":13},{"id":59,"name":"iPhone","slug":"iphone","count":13},{"id":113,"name":"Flow","slug":"flow","count":12},{"id":43,"name":"SharePoint Online","slug":"sharepoint-online","count":12},{"id":28,"name":"BCS","slug":"bcs","count":11},{"id":80,"name":"Windows Phone 8","slug":"windows-phone-8","count":8},{"id":61,"name":"iOS","slug":"ios","count":7},{"id":38,"name":"Magazine Articles","slug":"magazine-articles","count":7},{"id":74,"name":"SharePoint Apps","slug":"sharepoint-apps","count":7},{"id":9,"name":"Workflow","slug":"workflow","count":7},{"id":22,"name":"Development Utilities","slug":"development-utilities","count":6},{"id":37,"name":"MSDN","slug":"msdn","count":6},{"id":25,"name":"Silverlight","slug":"silverlight","count":6},{"id":8,"name":"Virtual Environments","slug":"virtual-environments","count":5},{"id":30,"name":"External Content Types","slug":"external-content-types","count":4},{"id":72,"name":"SharePoint Hosted","slug":"sharepoint-hosted","count":4},{"id":13,"name":"Site Definitions","slug":"site-definitions","count":4},{"id":12,"name":"Site Templates","slug":"site-templates","count":4},{"id":44,"name":"SPO","slug":"spo","count":4},{"id":33,"name":"Visual Studio","slug":"visual-studio","count":4},{"id":55,"name":"WCM","slug":"wcm","count":4},{"id":128,"name":"CDS","slug":"cds","count":3},{"id":127,"name":"Ignite","slug":"ignite","count":3},{"id":115,"name":"SPFx","slug":"spfx","count":3},{"id":14,"name":"SSO","slug":"sso","count":3},{"id":117,"name":"Teams","slug":"teams","count":3},{"id":24,"name":"Hyper-V","slug":"hyper-v","count":2},{"id":126,"name":"IoT","slug":"iot","count":2},{"id":76,"name":"Mapping","slug":"mapping","count":2},{"id":56,"name":"Outlook","slug":"outlook","count":2},{"id":32,"name":"Sandbox","slug":"sandbox","count":2},{"id":21,"name":"SharePoint Certified Architect","slug":"sharepoint-certified-architect","count":2},{"id":11,"name":"SharePoint Designer","slug":"sharepoint-designer","count":2},{"id":108,"name":"SharePoint Framework","slug":"sharepoint-framework","count":2},{"id":34,"name":"Visual Web Parts","slug":"visual-web-parts","count":2},{"id":91,"name":"Xamarin","slug":"xamarin","count":2},{"id":27,"name":".NET Assembly Connector","slug":"net-assembly-connector","count":1},{"id":50,"name":"Access Services","slug":"access-services","count":1},{"id":35,"name":"Aptillon","slug":"aptillon","count":1},{"id":36,"name":"BCS FAQ","slug":"bcs-faq","count":1},{"id":39,"name":"Books","slug":"books","count":1},{"id":148,"name":"Claude","slug":"claude","count":1},{"id":131,"name":"Common Data Service","slug":"common-data-service","count":1},{"id":82,"name":"Community","slug":"community","count":1},{"id":52,"name":"Composites","slug":"composites","count":1},{"id":123,"name":"Containers","slug":"containers","count":1},{"id":92,"name":"Cordova","slug":"cordova","count":1},{"id":65,"name":"CSS3","slug":"css3","count":1},{"id":140,"name":"DIY","slug":"diy","count":1},{"id":124,"name":"Docker","slug":"docker","count":1},{"id":133,"name":"Flows","slug":"flows","count":1},{"id":75,"name":"Geolocation","slug":"geolocation","count":1},{"id":111,"name":"GitHub","slug":"github","count":1},{"id":125,"name":"HOW TO: Flow","slug":"how-to-flow","count":1},{"id":62,"name":"HTML5","slug":"html5","count":1},{"id":49,"name":"InfoPath Forms Services","slug":"infopath-forms-services","count":1},{"id":64,"name":"JavaScript","slug":"javascript","count":1},{"id":63,"name":"JQuery","slug":"jquery","count":1},{"id":66,"name":"JQuery Mobile","slug":"jquery-mobile","count":1},{"id":31,"name":"Lists","slug":"lists","count":1},{"id":69,"name":"Mashups","slug":"mashups","count":1},{"id":19,"name":"MCA","slug":"mca","count":1},{"id":18,"name":"MCM","slug":"mcm","count":1},{"id":79,"name":"Nofifications","slug":"nofifications","count":1},{"id":105,"name":"Office","slug":"office","count":1},{"id":95,"name":"Office Add-ins","slug":"office-add-ins","count":1},{"id":78,"name":"Office Web Apps Server","slug":"office-web-apps-server","count":1},{"id":130,"name":"Operations","slug":"operations","count":1},{"id":129,"name":"PowerShell","slug":"powershell","count":1},{"id":15,"name":"QuickLaunch","slug":"quicklaunch","count":1},{"id":29,"name":"Search","slug":"search","count":1},{"id":107,"name":"SharePoint 2016","slug":"sharepoint-2016","count":1},{"id":71,"name":"SharePoint App","slug":"sharepoint-app","count":1},{"id":20,"name":"SharePoint Certified Master","slug":"sharepoint-certified-master","count":1},{"id":17,"name":"SharePoint Master Certification","slug":"sharepoint-master-certification","count":1},{"id":109,"name":"SharePoint Mobile App","slug":"sharepoint-mobile-app","count":1},{"id":77,"name":"SharePoint Saturday","slug":"sharepoint-saturday","count":1},{"id":73,"name":"SP APP","slug":"sp-app","count":1},{"id":70,"name":"SPAPP","slug":"spapp","count":1},{"id":81,"name":"SPS Events","slug":"sps-events","count":1},{"id":67,"name":"SSS","slug":"sss","count":1},{"id":16,"name":"Top Navigation","slug":"top-navigation","count":1},{"id":94,"name":"Training","slug":"training","count":1},{"id":134,"name":"Twitter","slug":"twitter","count":1},{"id":93,"name":"Universal","slug":"universal","count":1},{"id":114,"name":"Windows Phone","slug":"windows-phone","count":1},{"id":51,"name":"Workflows","slug":"workflows","count":1},{"id":53,"name":"WP7; SharePoint; SharePoint 2010; Social; Mobile","slug":"wp7-sharepoint-sharepoint-2010-social-mobile","count":1},{"id":147,"name":"XCode","slug":"xcode","count":1}],"recentPosts":[{"id":2222,"slug":"how-to-reauthenticate-claude-in-xcode","title":"HOW TO: Reauthenticate Claude in XCode","content":"\n

If you set up XCode to integrate with Claude you may find the OAuth token expires and the chat in XCode cannot communicate with Claude, then you see this error message.

OAuth token has expired. Please obtain a new token or refresh your existing token.

\n\n\n\n

\n\n\n\n

To resolve this issue quickly open XCode Settings > Intelligence.

\n\n\n\n

Click the ellipses next to your account, and select Sign Out.

\n\n\n\n

\n\n\n\n

Click the ellipses again and select Sign In.

\n\n\n\n

This will open a web browser where you can sign in and click Authorize.

\n\n\n\n

Restart XCode.

\n\n\n\n

\n\n\n\n

Happy coding!

\n","excerpt":"

If you set up XCode to integrate with Claude you may find the OAUth token expires and the chat in XCode cannot communicate with Claude. Here's how to fix it.

","date":"2026-04-01T21:22:55","modified":"2026-04-01T21:22:57","author":"Todd Baginski","authorSlug":"todd","categories":[{"id":146,"name":"AI","slug":"ai","count":1}],"tags":[{"id":148,"name":"Claude","slug":"claude","count":1},{"id":10,"name":"Custom Development","slug":"custom-development","count":87},{"id":147,"name":"XCode","slug":"xcode","count":1}],"featuredImage":"/blog/uploads/2026/04/xcode-claude.png","status":"publish"},{"id":2165,"slug":"how-to-disable-turn-off-a-power-platform-managed-environment","title":"HOW TO: Disable/Turn Off a Power Platform Managed Environment","content":"\n

What do you do if you accidentally enabled a Managed Environment in the Power Platform and you want to make the Environment non-Managed again? There is no way in the Power Platform Admin Center to Disable / Turn Off a Managed Environment, you can only Enable or Delete Managed Environments in the Admin Center. To Disable / Turn Off a Managed Environment, and go back to a non-Managed Environment, you must use PowerShell. Here's how to do it:

\n\n\n\n

Open a PowerShell prompt as Administrator.

\n\n\n\n

Install PowerShell

\n\n\n\n

Install-Module -Name Microsoft.PowerApps.Administration.PowerShell

\n\n\n\n

Log in with an account that has permissions to administer Environments. The following command will open an authentication prompt. The prompt supports MFA.

\n\n\n\n

Add-PowerAppsAccount -Endpoint prod

\n\n\n\n

Run this code that sets protectionLevel to Basic, which turns an Environment from Managed to non-Managed.

\n\n\n\n

$UpdatedGovernanceConfiguration = [pscustomobject]@{ protectionLevel = \"Basic\" }

\n\n\n\n

Run this command to apply the changes to the Environment you want to convert from Managed to non-Managed. Make sure to replace the Environment Id accordingly.

\n\n\n\n

Set-AdminPowerAppEnvironmentGovernanceConfiguration -EnvironmentName -UpdatedGovernanceConfiguration $UpdatedGovernanceConfiguration

\n\n\n\n

Here's what it all looks like:

\n\n\n\n

\n\n\n\n

Here's the Microsoft documentation that describes part of this process.

\n\n\n\n

https://learn.microsoft.com/en-us/power-platform/admin/managed-environment-enable#disable-managed-environments-using-powershell

\n\n\n\n

\n","excerpt":"

What do you do if you accidentally enabled a Managed Environment in the Power Platform and you want to make the Environment non-Managed again?

","date":"2024-10-15T16:47:48","modified":"2024-10-15T16:47:49","author":"Todd Baginski","authorSlug":"todd","categories":[{"id":103,"name":"Cloud","slug":"cloud","count":68},{"id":120,"name":"Flow","slug":"flow","count":18},{"id":104,"name":"Office 365","slug":"office-365","count":80},{"id":121,"name":"PowerApps","slug":"powerapps","count":57}],"tags":[{"id":42,"name":"Cloud","slug":"cloud","count":46},{"id":10,"name":"Custom Development","slug":"custom-development","count":87},{"id":5,"name":"Helpful Code","slug":"helpful-code","count":70},{"id":122,"name":"HOW TO: PowerApps","slug":"how-to-powerapps","count":38},{"id":54,"name":"Mobile","slug":"mobile","count":66},{"id":112,"name":"PowerApps","slug":"powerapps","count":56}],"featuredImage":"/blog/uploads/2024/10/sunset-ocean.jpg","status":"publish"},{"id":2143,"slug":"how-to-make-a-diy-lacrosse-goal-transporter","title":"HOW TO: Make a DIY lacrosse goal transporter","content":"\n

There are several products on the market that make it easy to move your lacrosse goal. I investigated them and then created my own to save my yard, my back, and my money. An added bonus is you can store your goal on the transporter to keep it off the ground and free from dirt and moisture.

\n\n\n\n

This is especially helpful if you have ECD targets, a Smart Backstop shooting net, and a Lax Dog strapped to your goal, which makes it quite heavy! These are not affiliate links, I don't make any money off them. Just thought I'd share the links because we really enjoy these products.

\n\n\n\n

Hopefully this article helps out my brothers and sisters in the lax community.

\n\n\n\n

\n\n\n\n

Parts

\n\n\n\n

1 - 4x4x8' #2 Ground Contact Green pressure-treated timber - $10.30

\n\n\n\n

1 - 2x4x8' #2 Ground Contact Green pressure treated lumber - $3.89

\n\n\n\n

1 - 21\" #2 Ground Contact Green pressure-treated timber - $0.00 *

\n\n\n\n

19 - #9 2 1/2\" coated deck screws - $0.00 *

\n\n\n\n

2 - 5/8\" x 8\" galvanized lag screws - $3.39 (these become the wheel axles)

\n\n\n\n

2 - 8\" Pneumatic Utility Tire (no flat) - $20.57 (comes with plastic spacers - you could cut a small pipe to make a spacer too)

\n\n\n\n

* Already had these items in my shop from previous projects.

\n\n\n\n

Total: $38.15

\n\n\n\n

Instructions

\n\n\n\n

Lay the goal on top of the 4x4.

\n\n\n\n

Mark the 4x4 where you want to cut it. Leave a little room on the ends to install a stopper (scroll down to see the picture with the stopper) to prevent the goal from sliding off the end. I left about 2\" of space on either side of the goal.

\n\n\n\n

Cut the 4x4 to the length that makes sense for your goal. I went with 80\" for my 4x4.

\n\n\n\n

Mark the center of each end of the 4x4. Then use a 7/16\" (or the appropriate size bit that is small enough that the threads on the lag screw will still bite into the wood) drill bit to drill a hole as deep as the threads on your lag screw. The lag screws are the axles for the wheels. In my case I used a boring bit, and the hole was over 4\" deep. This is the most important step. If you drill this hole off-center or off-axis the tires will not be aligned properly. If the pressure treated wood is fresh and wet, this could be challenging. Take your time, get it right the first time.

\n\n\n\n

Use a large socket wrench to screw the lag screws into the 4x4 until all the threads are engaged. Don't put your wheel or spacer on yet. Leave them off so you can concentrate on screwing in the screw perfectly. This is the 2nd most important step. If you screw it in on an angle, the tires will not be aligned properly. This is not easy; you will need to put a lot of muscle into this.

\n\n\n\n

Use a large socket wrench to un-screw the lag screws from the 4x4 all the way. Be careful when you take out the lag screw, it could be quite hot from the friction.

\n\n\n\n

Lay the goal on top of the 4x4 and center it.

\n\n\n\n

This picture shows the pieces described in the next set of steps.

\n\n\n\n

\n\n\n\n

Cut some of the 21\" 2x4 to make little stoppers for top ends of the 4x4. You will do this 2 times, one for each end.

\n\n\n\n

Align the stopper on top of the 4x4 and drill holes in the 2x4 stopper you just made. Go all the way through so you mark the 4x4 with holes. Remove the stopper and finish drilling out the holes in the 4x4. You will do this 2 times, one for each end.

\n\n\n\n

Screw the stoppers to the 4x4 with the deck screws. You will do this 2 times, one for each end.

\n\n\n\n

Cut some 2x4 to make a brace for the goal posts to prevent the goal from sliding off the 4x4. I made my braces 8\" long. You will do this 2 times, one for each goal post.

\n\n\n\n

Align the brace on the side of the 4x4 and drill holes in the 2x4 braces you just made. Go all the way through so you mark the 4x4 with holes. Remove the brace and finish drilling out the holes in the 4x4. You will do this 2 times, one for each end.

\n\n\n\n

Screw the brace to the 4x4 with the deck screws. You will do this 2 times, one for each end.

\n\n\n\n

This picture shows the pieces described in the next set of steps.

\n\n\n\n

\n\n\n\n

Align the 2x4 in the middle of the 4x4 make the end flush to the edge of the 4x4. Drill holes in the 2x4 and go all the way through so you mark the 4x4 with holes. Remove the brace and finish drilling out the holes in the 4x4.

\n\n\n\n

Screw the 2x4 to the 4x4 with the deck screws.

\n\n\n\n

This picture shows the pieces described in the next set of steps.

\n\n\n\n

\n\n\n\n

Pass the lag screw through the wheel, add the spacer on the other side, then use the large socket wrench to tighten the screw. You will do this 2 times, one for each end.

\n\n\n\n

Walk around the back of your goal and grab the 2x4 and lift up the goal.

\n\n\n\n

\n\n\n\n

Now, add a little flair and make it easier to lift the 2x4 by adding a custom handle. This beauty was made by my Dad when he created our treehouse when I was a boy. It lives on today as part of our lacrosse transporter! I attached it with 2 deck screws.

\n\n\n\n

\n\n\n\n

Move your goal to a suitable location and rip some Gs!

\n\n\n\n

\n\n\n\n

Here are some more pictures that show everything from a few different angles.

\n\n\n\n

\n\n\n\n

\n\n\n\n

\n\n\n\n

\n\n\n\n

\n","excerpt":"

There are several products on the market that make it easy to move your lacrosse goal. I investigated them and then created my own to save my yard, my back, and my money.

","date":"2024-09-23T22:29:27","modified":"2024-11-20T16:48:07","author":"Todd Baginski","authorSlug":"todd","categories":[{"id":139,"name":"Lacrosse","slug":"lacrosse","count":1}],"tags":[{"id":140,"name":"DIY","slug":"diy","count":1}],"featuredImage":"/blog/uploads/2024/09/fi.jpg","status":"publish"},{"id":2117,"slug":"accelerate-development-with-the-catalog-for-power-platform","title":"Accelerate development with the Catalog for Power Platform","content":"\n

This video demonstrates how to accelerate development with the Catalog for Power Platform in both green field (creating a new app from scratch) and enhancement (taking an existing app and updating it) scenarios.

\n\n\n\n

In this video you will learn how to add Solutions to the Catalog and how to deploy them to Power Platform environments. You will also learn how to organize your Solutions and reusable components to enable quick app development and streamlined enhancements and maintenance.

\n\n\n\n

\n","excerpt":"

Learn how to accelerate development with the Catalog for Power Platform in both green field (creating a new app from scratch) and enhancement (taking an existing app and updating it) scenarios.

","date":"2023-05-25T13:30:00","modified":"2023-05-25T17:49:54","author":"Todd Baginski","authorSlug":"todd","categories":[{"id":103,"name":"Cloud","slug":"cloud","count":68},{"id":120,"name":"Flow","slug":"flow","count":18},{"id":104,"name":"Office 365","slug":"office-365","count":80},{"id":121,"name":"PowerApps","slug":"powerapps","count":57}],"tags":[{"id":42,"name":"Cloud","slug":"cloud","count":46},{"id":10,"name":"Custom Development","slug":"custom-development","count":87},{"id":5,"name":"Helpful Code","slug":"helpful-code","count":70},{"id":122,"name":"HOW TO: PowerApps","slug":"how-to-powerapps","count":38},{"id":54,"name":"Mobile","slug":"mobile","count":66}],"featuredImage":"/blog/uploads/2019/08/succulent-garden.jpg","status":"publish"},{"id":2125,"slug":"what-is-the-catalog-for-power-platform","title":"What is the Catalog for Power Platform?","content":"\n

In this video you will learn the basics about the Catalog for Power Platform and how the Catalog for Power Platform accelerates development and promotes consistency by making it easy for makers to discover and reuse Power Platform components.

\n\n\n\n

After you watch this video, check out these other great videos about the Catalog for Power Platform and related concepts.

\n\n\n\n

Accelerate development with the Catalog for Power Platform

\n\n\n\n

Sharing PCF Components with the Catalog in Power Platform

\n\n\n\n

Power Platform ALM - Choose the Right Approach

\n\n\n\n

\n","excerpt":"

Learn the basics about the Catalog for Power Platform and how the Catalog for Power Platform accelerates development.

","date":"2023-05-25T13:30:00","modified":"2023-05-25T17:52:48","author":"Todd Baginski","authorSlug":"todd","categories":[{"id":103,"name":"Cloud","slug":"cloud","count":68},{"id":120,"name":"Flow","slug":"flow","count":18},{"id":104,"name":"Office 365","slug":"office-365","count":80},{"id":121,"name":"PowerApps","slug":"powerapps","count":57}],"tags":[{"id":42,"name":"Cloud","slug":"cloud","count":46},{"id":10,"name":"Custom Development","slug":"custom-development","count":87},{"id":5,"name":"Helpful Code","slug":"helpful-code","count":70},{"id":122,"name":"HOW TO: PowerApps","slug":"how-to-powerapps","count":38},{"id":54,"name":"Mobile","slug":"mobile","count":66},{"id":112,"name":"PowerApps","slug":"powerapps","count":56}],"featuredImage":"/blog/uploads/2018/01/Ducks-Little-Miami.jpg","status":"publish"}]}},"actionData":null,"errors":null}

CategoryOffice

Creating and deploying VSTO Documents inside SharePoint Document Libraries