Comments for Thomas F. Abraham - On Technology http://www.tfabraham.com/blog Visual Studio, .NET, BizTalk Server, SQL Server and more... Mon, 12 Oct 2009 16:24:06 -0600 http://wordpress.org/?v=2.8.1 hourly 1 Comment on Error Upgrading a Solution to BizTalk 2009: Child element <BIZTALK> of element <VisualStudioProject> is not valid by Andy M http://www.tfabraham.com/blog/2009/07/error-upgrading-a-solution-to-biztalk-2009-child-element-of-element-is-not-valid/comment-page-1/#comment-165 Andy M Mon, 12 Oct 2009 16:24:06 +0000 http://www.tfabraham.com/blog/?p=220#comment-165 Check this out: http://stackoverflow.com/questions/1110465/visual-studio-2008-sp1-and-upgrading-a-biztalk-2006-r2-project-to-biztalk-2009-pr Check this out: http://stackoverflow.com/questions/1110465/visual-studio-2008-sp1-and-upgrading-a-biztalk-2006-r2-project-to-biztalk-2009-pr

]]> Comment on Error Upgrading a Solution to BizTalk 2009: Child element <BIZTALK> of element <VisualStudioProject> is not valid by dino http://www.tfabraham.com/blog/2009/07/error-upgrading-a-solution-to-biztalk-2009-child-element-of-element-is-not-valid/comment-page-1/#comment-162 dino Tue, 29 Sep 2009 12:48:56 +0000 http://www.tfabraham.com/blog/?p=220#comment-162 Got the same issue with solutions not in source control. Am using the Nant framework moving from bts 2006 (not r2) to bts 2009 64 bit! Will likely go down the recreate and add resources route, but what a pain in the butt. Any solutions to this? Got the same issue with solutions not in source control. Am using the Nant framework moving from bts 2006 (not r2) to bts 2009 64 bit!

Will likely go down the recreate and add resources route, but what a pain in the butt. Any solutions to this?

]]> Comment on Choosing a WPF Data Grid Control by Alex http://www.tfabraham.com/blog/2007/12/choosing-a-wpf-data-grid-control/comment-page-1/#comment-5 Alex Tue, 19 May 2009 04:47:06 +0000 http://www.tfabraham.com/blog/?p=107#comment-5 I am actually quite familiar with Infragistics, and their WPF stuff is all developed in eastern Europe, which is probably the reason no one responds. That's the price of outsourcing. I am actually quite familiar with Infragistics, and their WPF stuff is all developed in eastern Europe, which is probably the reason no one responds. That’s the price of outsourcing.

]]> Comment on If Your Visual Studio Solutions Open Slowly, Check WebsiteCache by Ryan Shaw http://www.tfabraham.com/blog/2009/01/if-your-visual-studio-solutions-open-slowly-check-websitecache/comment-page-1/#comment-4 Ryan Shaw Tue, 19 May 2009 04:43:49 +0000 http://www.tfabraham.com/blog/?p=121#comment-4 Hey Tom, I've had this very same problem, I was always wondering why VS was getting so slow! Nice find! Hey Tom,

I’ve had this very same problem, I was always wondering why VS was getting so slow! Nice find!

]]> Comment on URL Case-Sensitivity on WCF Web Services Published from BizTalk 2006 R2 to IIS by sixeyed http://www.tfabraham.com/blog/2008/03/url-case-sensitivity-on-wcf-web-services-published-from-biztalk-2006-r2-to-iis/comment-page-1/#comment-3 sixeyed Tue, 19 May 2009 04:42:29 +0000 http://www.tfabraham.com/blog/?p=113#comment-3 Found the same result with a different issue, the IIS metabase had the app root in uppercase (c:\windows\system32\inetsrv\metabase.xml in Win2003). Changed from this: <IIsWebVirtualDir Location ="/LM/W3SVC/1/ROOT/App.Service.Name" AppFriendlyName="App.Service.Name"" AppRoot="/LM/W3SVC/1/ROOT/APP.SERVICE.NAME" to this: <IIsWebVirtualDir Location ="/LM/W3SVC/1/ROOT/App.Service.Name" AppFriendlyName="App.Service.Name"" AppRoot="/LM/W3SVC/1/ROOT/App.Service.Name" , ran IISRESET and all well. Found the same result with a different issue, the IIS metabase had the app root in uppercase (c:\windows\system32\inetsrv\metabase.xml in Win2003). Changed from this:

Location =”/LM/W3SVC/1/ROOT/App.Service.Name”

AppFriendlyName=”App.Service.Name”"

AppRoot=”/LM/W3SVC/1/ROOT/APP.SERVICE.NAME”

to this:

Location =”/LM/W3SVC/1/ROOT/App.Service.Name”

AppFriendlyName=”App.Service.Name”"

AppRoot=”/LM/W3SVC/1/ROOT/App.Service.Name”

, ran IISRESET and all well.

]]> Comment on If Your Visual Studio Solutions Open Slowly, Check WebsiteCache by Rajib Bahar http://www.tfabraham.com/blog/2009/01/if-your-visual-studio-solutions-open-slowly-check-websitecache/comment-page-1/#comment-2 Rajib Bahar Tue, 19 May 2009 04:40:45 +0000 http://www.tfabraham.com/blog/?p=121#comment-2 Their bug reporting is a bit contradictory. It says status is Close (Not Reproducible)... If we look below that page Steps to Reproduce Make a solution with hundreds of projects. Open and close it and check out the WebSiteCache folder above. Their bug reporting is a bit contradictory. It says status is Close (Not Reproducible)…

If we look below that page

Steps to Reproduce

Make a solution with hundreds of projects. Open and close it and check out the WebSiteCache folder above.

]]> Comment on .NET Framework 1.1 and 2.0 Side-by-Side (SxS) by senthil kumar http://www.tfabraham.com/blog/2005/12/net-framework-11-and-20-side-by-side-sxs/comment-page-2/#comment-155 senthil kumar Wed, 07 Jan 2009 09:43:06 +0000 http://www.tfabraham.com/blog/?p=29#comment-155 Very useful information. now i can run framework1.1 and 2.0 web applicagtion on same iis6 server. what i did 1.I Created new application pool 2.This application pool configurated on my application website (framework 1.1) 3.I added following code on web.config <startup> <supportedRuntime version="v1.1.4322" /> </startup> 4. set aps.net version 1.1 in my web site. Thanks senthil Kumar esenthil.erd@gmail.com Very useful information.

now i can run framework1.1 and 2.0 web applicagtion on same iis6 server.

what i did

1.I Created new application pool

2.This application pool configurated on my application website (framework 1.1)

3.I added following code on web.config

<startup>

<supportedRuntime version=”v1.1.4322″ />

</startup>

4. set aps.net version 1.1 in my web site.

Thanks

senthil Kumar

esenthil.erd@gmail.com

]]> Comment on URL Case-Sensitivity on WCF Web Services Published from BizTalk 2006 R2 to IIS by Elton http://www.tfabraham.com/blog/2008/03/url-case-sensitivity-on-wcf-web-services-published-from-biztalk-2006-r2-to-iis/comment-page-1/#comment-158 Elton Wed, 05 Nov 2008 12:20:42 +0000 http://www.tfabraham.com/blog/?p=113#comment-158 Certainly did, thanks Thomas - I hadn't thought to check the ASP.NET cache. Worth noting that if you modify the Receive Location (in desparation) to use the wrong case , you'll be able to navigate to the .svc file - but likely to have further issues with downstream code expecting the original case. Certainly did, thanks Thomas – I hadn’t thought to check the ASP.NET cache. Worth noting that if you modify the Receive Location (in desparation) to use the wrong case , you’ll be able to navigate to the .svc file – but likely to have further issues with downstream code expecting the original case.

]]> Comment on Optimize Large Data Transfer in Web Services with MTOM by Jeff Tressler http://www.tfabraham.com/blog/2006/12/optimize-large-data-transfer-in-web-services-with-mtom/comment-page-1/#comment-157 Jeff Tressler Thu, 18 Sep 2008 15:48:15 +0000 http://www.tfabraham.com/blog/?p=87#comment-157 This is interesting but does not seem to answer the "I frequently hear comments that Web services are inappropriate for carrying large data messages, say greater than 1 MB." comment. It deals with not having to expand a large message but wether you send a 3MB PDF in binary or a 4MB Base64 message, it is still greater then the magical 1MB limit. Now if I was sending a 1MB PDF and did not want to expand it to a 1.33 MB and thus pass the "limit" then the above is useful. But if I want to send a 54 MB XML message, what would be the options with respect to Web Services. That is what is needed with respect to the "Web services are inappropriate for carrying large data messages, say greater than 1 MB" understanding that people have. This is interesting but does not seem to answer the “I frequently hear comments that Web services are inappropriate for carrying large data messages, say greater than 1 MB.” comment.

It deals with not having to expand a large message but wether you send a 3MB PDF in binary or a 4MB Base64 message, it is still greater then the magical 1MB limit. Now if I was sending a 1MB PDF and did not want to expand it to a 1.33 MB and thus pass the “limit” then the above is useful.

But if I want to send a 54 MB XML message, what would be the options with respect to Web Services. That is what is needed with respect to the “Web services are inappropriate for carrying large data messages, say greater than 1 MB” understanding that people have.

]]> Comment on .NET Framework 1.1 and 2.0 and 3.0 Side-by-Side (SxS) by vikash http://www.tfabraham.com/blog/2006/12/net-framework-11-and-20-and-30-side-by-side-sxs/comment-page-1/#comment-156 vikash Wed, 17 Sep 2008 14:00:21 +0000 http://www.tfabraham.com/blog/?p=91#comment-156 Hi Thomas, I am running my .Net application on maching having .Net Framework 1.1 and 2.0 and it's working fine. But in other machine having .Net Framework 1.1, 2.0 Service Pack 1 and 3.0 Service Pack 1, this appliation is crashing with the below error. Any clue why this is happening, and what can I do for this. 2008-09-16 09:18:01,015 [7] ERROR Simias.Event.IProcEventSubscriber - 3975 : Error communication failure. System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host at System.Net.Sockets.Socket.BeginReceive(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags, AsyncCallback callback, Object state) at Simias.Event.IProcEventSubscriber.MessageHandler(IAsyncResult result) Hi Thomas,

I am running my .Net application on maching having .Net Framework 1.1 and 2.0 and it’s working fine. But in other machine having .Net Framework 1.1, 2.0 Service Pack 1 and 3.0 Service Pack 1, this appliation is crashing with the below error.

Any clue why this is happening, and what can I do for this.

2008-09-16 09:18:01,015 [7] ERROR Simias.Event.IProcEventSubscriber – 3975 : Error communication failure.

System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host

at System.Net.Sockets.Socket.BeginReceive(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags, AsyncCallback callback, Object state)

at Simias.Event.IProcEventSubscriber.MessageHandler(IAsyncResult result)

]]>