It has been a little over a year since we shipped VS 2008 and .NET FX 3.5.
Read the original here:
Delivering ongoing value
Delivering ongoing value
Technical Articles and White Papers on SQL Server
I will be attending an advanced SQL Server training in a couple of weeks and the instructors recommended some pre-reading.
Original post:
Technical Articles and White Papers on SQL Server
Learn how to integrate PeopleSoft, Outlook and MOSS
Office Business Application (OBA) development is growing in importance thus continues to be an integral part of the Office platform developer story. To that end, we recently completed a new resource that could be used for OBA training specific to PeopleSoft and Office integration. This HOL uses the OBA Starter Kit for PeopleSoft as the demo environment and provides a comprehensive walkthrough on how to a) create web services that wrap around PeopleSoft components (both native and custom), b) consume those services in a custom Outlook client (the design can be extrapolated to other Office custom clients), and c) integrate the service with the MOSS Business Data Catalog.
Read more:
Learn how to integrate PeopleSoft, Outlook and MOSS
OBA Part 2 – Building an Outlook Client against LOB Data
In the last couple posts we’ve been talking about an Office Business Application (OBA) architecture for the new Northwind Traders and how to expose line-of-business (LOB) data , in our case the Northwind SQL database, using ADO.NET Data Services . Today we’re going to talk about how to build an Outlook Add-In that pulls the order history from the database through our data service when a customer email arrives in the inbox of our sales reps.
View original here:
OBA Part 2 – Building an Outlook Client against LOB Data
OBA Part 1 – Exposing Line-of-Business Data
Last post I talked about the high-level architecture of our O ffice B usiness A pplication for the new Northwind Traders. There are a lot of different architecture options to consider when building an OBA. OBA is all about using Microsoft Office with your Line of Business (LOB) data.
Here is the original:
OBA Part 1 – Exposing Line-of-Business Data
Building an Office Business Application for TechReady 8
The last week I've been working with a couple teammates on an Office Business Application (OBA) demonstration we wanted to put together for TechReady 8. TechReady is an internal conference we deliver to the field employees. It's my first one and so far it's been pretty fun
See more here:
Building an Office Business Application for TechReady 8
Tomorrow’s Microsoft BI Platform
Read more from the original source:
Tomorrow’s Microsoft BI Platform
Tomorrow’s Business Intelligence Platform One of my favorite aspects about Microsoft is the company never stands still from a product development standpoint. The company is constantly driving innovation and releasing new products to the market
Open Source – “Because we can fix it if it breaks”
I had the opportunity recently to write an editorial for CIO.com espousing reasons for adopting the Windows platform.
My current project at the time involved building a Single Sign-On architecture. A key requirement for the project was it had to provide capabilities for sending and receiving SSO requests to and from their partners.
We, (my team at Cogent Company) had it all mapped out using Windows Server along with Active Directory Federation Services (ADFS). We even found a great partner that could handle the integration of Windows with other platforms (i.e. IBM, SUN, Linux/Unix, etc.).
Our best laid plans were soon changed when we started working with my client’s partners. They decided against implementing our architecture (which would require minimal changes to their code base) in favor of open-source technologies. One partner’s justification for their decision was, "because if it breaks, we can fix it".
Nice. If only their boss could have this rationale. What manager or executive wouldn’t want their people fixing open-source software? I wonder how this situation would play itself out in actuality? In their status report would they cite as their reason for not completing their work as, "unavoidable delays caused by the need to correct open source the open-source application we chose that doesn’t work?"
I realize this attitude is not shared by everyone who prefer to use open-source technologies. But in my experience I have run into enough to decide this attitude is just plain stupid.
Why not just implement something that works once deployed and is backed by a real company…not a bunch of techno-wizards that like to experiment with their code?
Nutso!