Microsoft wants to help you convert from Notes to .Net...
Category Microsoft
Declan found a new Microsoft document that is a migration guide to move from Notes to .Net. I saw his posting this morning, but I just now got home from work and have a chance to post about this. I'm going to read all 169 pages (a lot of pages for something that's supposed to be easy) and do an analysis of it, but I'll quote the same passage that Ed Brill did. It's in the introduction, 2nd paragraph, and I think this tells me a lot as to where this document is going to be going...
Notes/Domino R6 is the last planned release of the existing Notes architecture; IBM plans to reengineer it to run on top of DB2 and WebSphere. The change in database structure creates a significant migration effort for existing customers and creates a situation where the Notes/Domino direction is re-evaluated. Additionally, IBM has halted plans for long-awaited improvements to Notes/Domino, and users are getting conflicting timelines for their replacement strategy. These problems have been amplified by IBM's lack of direction for a cohesive coexistence and migration strategy. Accordingly, many organizations are expressing interest in migrating away from the moribund Notes/Domino platform, but they do not want to abandon their existing investment in applications built on the Notes architecture.
I don't think I've seen so many lies and misdirection in a single paragraph. Microsoft is outdoing themselves of late.
Of course, we can write our own .Net to Notes paper and include our own 2nd paragraph. It would go something... like... this...
Exchange 2003 is the last planned release of the existing Exchange architecture; Microsoft plans to reengineer it to run on top of WinFS or Yukon (they haven't decided yet). The change in database structure creates a significant migration effort for existing customers and creates a situation where the Exchange direction is re-evaluated. Additionally, Microsoft has halted plans for long-awaited improvements to Exchange, and users are getting no timelines for their replacement strategy. These problems have been amplified by Microsoft's lack of direction for a cohesive coexistence and migration strategy from earlier version of Exchange. Accordingly, many organizations are expressing interest in migrating away from the Exchange platform. Thankfully, Exchange was so abssymal as an application development platform that migration of applications is not an issue.
Declan found a new Microsoft document that is a migration guide to move from Notes to .Net. I saw his posting this morning, but I just now got home from work and have a chance to post about this. I'm going to read all 169 pages (a lot of pages for something that's supposed to be easy) and do an analysis of it, but I'll quote the same passage that Ed Brill did. It's in the introduction, 2nd paragraph, and I think this tells me a lot as to where this document is going to be going...
Notes/Domino R6 is the last planned release of the existing Notes architecture; IBM plans to reengineer it to run on top of DB2 and WebSphere. The change in database structure creates a significant migration effort for existing customers and creates a situation where the Notes/Domino direction is re-evaluated. Additionally, IBM has halted plans for long-awaited improvements to Notes/Domino, and users are getting conflicting timelines for their replacement strategy. These problems have been amplified by IBM's lack of direction for a cohesive coexistence and migration strategy. Accordingly, many organizations are expressing interest in migrating away from the moribund Notes/Domino platform, but they do not want to abandon their existing investment in applications built on the Notes architecture.
I don't think I've seen so many lies and misdirection in a single paragraph. Microsoft is outdoing themselves of late.
Of course, we can write our own .Net to Notes paper and include our own 2nd paragraph. It would go something... like... this...
Exchange 2003 is the last planned release of the existing Exchange architecture; Microsoft plans to reengineer it to run on top of WinFS or Yukon (they haven't decided yet). The change in database structure creates a significant migration effort for existing customers and creates a situation where the Exchange direction is re-evaluated. Additionally, Microsoft has halted plans for long-awaited improvements to Exchange, and users are getting no timelines for their replacement strategy. These problems have been amplified by Microsoft's lack of direction for a cohesive coexistence and migration strategy from earlier version of Exchange. Accordingly, many organizations are expressing interest in migrating away from the Exchange platform. Thankfully, Exchange was so abssymal as an application development platform that migration of applications is not an issue.
| Permalink |
