Skip to main content

Mid-Ohio Connected Systems Developers User Group - Delbert Murphy

Man, I'm pissed to miss this. (I'll be at CINNUG Thursday watching Randy Pagels speak on ALM.)

Monish announced the inaugural MOCSDUG meeting--and they landed Delbert Murphy! I've not seen him speak but he's well known and carries a very positive reputation. Hopefully, I'll catch the live meeting. Details below.



Introducing MOCSDUG (Mid-Ohio Connected Systems Developers User Group)
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
The Mid-Ohio Connected Systems Developers User Group (MOCSDUG) has formed to facilitate education and knowledge exchange around topics of Business Process and Enterprise Integration. The group will specifically focus on the Microsoft Connected Systems product stack which includes: BizTalk Server, WF, WCF and other related technologies. The MOCSDUG seeks to connect developers, architects, and IT decision makers in the Mid-Ohio region with best practices, architectural concepts, and case studies. The group will work very closely with Microsoft and its community leaders to deliver the latest information on BizTalk Server, WF, and WCF. The MOCSDUG will strive to remain agile by evolving as technology changes to meet the needs of its members.
Microsoft’s Project Oslo: Past, Present, Future By Delbert Murphy
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
When: Thursday, April 3rd, 2008, 6:00pm - 8:00pm
Where: Microsoft Office - Columbus (Address Below)
Now that code from Microsoft’s project Oslo is being demonstrated to Analysts from firms like Gartner and Forrester—and those analysts are actually excited about what they see—people in the Information Technology industry are starting to wonder if Oslo really will change the landscape of how application software is designed, developed, deployed and managed. Delbert Murphy, a BizTalk Technical Specialist and SOA Insider from Microsoft Corporation, will discuss the roots and the direction of Microsoft’s project Oslo—and most importantly—how this new paradigm in the software lifecycle will affect you.
To learn more about Oslo prior to the meeting, visit: http://www.microsoft.com/soa/products/oslo.aspx.
Directions to the Meeting
-=-=-=-=-=-=-=-=-=-=-=-=-=-=
The MOCSDUG meets at the Microsoft office on the North side of Columbus, OH at Polaris Center.
Address: Polaris Center, 8800 Lyra Dr. 4th Floor, Columbus, OH 43240
Can't make it in person?
-=-=-=-=-=-=-=-=-=-=-=-=-=
Delbert Murphy has invited you to attend an online meeting using
Microsoft Office Live Meeting.
AUDIO INFORMATION
Conference call:
Number: 1-866-500-6738
Participant Passcode: 4968936
FIRST-TIME USERS
To save time before the meeting, check your system to make sure it is
ready to use Microsoft Office Live Meeting.
TROUBLESHOOTING
Unable to join the meeting? Follow these steps:
1. Copy this address and paste it into your web browser:
2. Copy and paste the required information:
Meeting ID: D5T4T5
Entry Code: FxB4@}9/D
If you still cannot enter the meeting, contact support:
NOTICE
Microsoft Office Live Meeting can be used to record meetings.
By participating in this meeting, you agree that your communications
may be monitored or recorded at any time during the meeting.
Contact Information
-=-=-=-=-=-=-=-=-=-=-=-
If you have any questions about the Mid-Ohio Connected Systems Developers User Group (MOCSDUG) or the upcoming meeting, please contact Monish Nagisetty at mnagisetty@gmail.com. MOCSDUG is currently in the process of setting up its website. Please stay tuned to the mailing list for more details on the site.

Comments

Popular posts from this blog

Shrinking WSS (Sharepoint) SQL Server Log Files

Yesterday, while migrating a source repository from StarTeam to TFS, I received the following error:
"TF30042: The database is full. Contact your Team Foundation Server administrator."Excuse you? Sure enough, my 100+ GB drive was full on the server. But I'd only migrated around 1000 items. Surely SQL wasn't consuming 100MB per file.

Turns out (yes, there was a lot of crud on the drive but...) the majority of the space, almost 40GB was being consumed by the Windows Sharepoint Services WSS Content data and log SQL Server files. Huh? I still need to investigate and understand why this portal, which is 100% unused, grew so large. Regardless, here's what I did to resolve:

Since this is not yet a production database, I flipped the SQL recovery option from Full to Simple for WSS Content and several other databases. Detail here and here.
Executed the maintenance plan for all the databases to get backups and clear out some of these files. That didn't help much. The Auto_…

TFS Error | The type initializer for 'Microsoft.TeamFoundation.Build.Server.BuildInformationNodeBinder' threw an exception.

Posting this one for the search engines. If you ever receive the exception "The type initializer for 'Microsoft.TeamFoundation.Build.Server.BuildInformationNodeBinder' threw an exception.", more than likely, your drive space is at 0 on your TFS application tier box.

I encountered this at a client recently. The root cause was that IIS logs had filled up the OS drive (C:\). I switched IIS logging to the applications drive (D:\) which cleaned up the OS drive and resolved the issue.

Detailed message:


TF53010: The following error has occurred in a Team Foundation component or extension:


Date (UTC): 6/7/2011 4:18:53 PM

Machine: TFSATBOX

Application Domain: /LM/W3SVC/8080/ROOT/tfs-1-129519118182628600

Assembly: Microsoft.TeamFoundation.Framework.Server, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a; v2.0.50727

Service Host: 7ecfbd77-b386-4d75-b038-b05474782696 (DefaultCollection)

Process Details:

Process Name: w3wp

Process Id: 3676

Thread Id: 5752

Ac…

Code Analysis Invalid Settings Error When Invoked from within VSTS

This issue plagued me for several hours today so I'm posting my resolution. Executing Code Analysis from within Visual Studio Team System - Team Suite kept reporting:
"Invalid settings passed to CodeAnalysis task. See output window for details."
MSBuild is unable to locate the correct binaries to perform Code Analysis on managed binaries. Make sure that either Visual Studio Team System 2008 Development Edition or Visual Studio Team System 2008 Team Suite is installed with the Code Analysis feature. If MSBuild is being run from within the "Visual Studio Command Prompt", specify the path to your analysis binaries by setting the FXCOPDIR environment variable. At first, after a search, I thought it was an Environment Variable issue regarding the path to FxCopCmd.exe. Very helpful post here. However, after adding the Environment Variable FxCopDir, I was closer but still getting an error.

Finally, I took the FxCopCmd.exe command line string into a command window and…