You searched for the word(s): userid:215442

More Search Options

RSS Available

• Re: problem in receiving msmq private remote queue

  Is the application reading the queue running under a domain user? I'm assuming both machines are part of the same domain, right?

  Posted to Enterprise Services Integration (Forum) by tomasr on 9/29/2006

• Re: problem in receiving msmq private remote queue

  How are you referencing the queue in your code (i.e. the path/format string)? And what error are you getting? Do be aware that if the queue is transactional, you won't be able to read it this way, as MSMQ does not support remote transactional reads.

  Posted to Enterprise Services Integration (Forum) by tomasr on 9/28/2006

• Re: Consume a web service from code with only the wsdl file available

  I'm not sure I understand what the problem is... if you have the WSDL, then that's enough to generate a client side proxy using the built-in Add Web Reference wizard or wsdl.exe. Is that a problem?

  Posted to XML Web Services (Forum) by tomasr on 7/19/2006

• Re: Configuration & Implementaion of Biztalk 2006

  Jai, Regarding the IDE thing: You usually install BizTalk *after* you install VS. If you installed them in the wrong order, you can go to Add/Remove Programs, and use the BizTalk installer to add the SDK and developer tools to your VS installation. As for the other stuff, check your machine's event log; chances are your AppPool is not starting and that should give you a clue why.

  Posted to Enterprise Services Integration (Forum) by tomasr on 6/28/2006

• Re: web aplication with win sock

  If you already coded the socket connection using vb.net, this shouldn't be much different (depending on your needs). Changes are you can use the TcpClient class for this ( here's an example )

  Posted to Enterprise Services Integration (Forum) by tomasr on 4/18/2006

• Re: Reg-Free COM ('isolated' property in reference)

  I do now know if this will work on ASP.NET phil, but you could try adding the reference to a standard console or winforms project, set the property, compile and then just grab the generated manifest and deploy it with your asp.net project. Worth a try, maybe?

  Posted to Enterprise Services Integration (Forum) by tomasr on 4/17/2006

• Re: web aplication with win sock

  You can certainly use winsock still in this scenario by having your asp.net app do the connection to the remote application using sockets. You should even be able to reuse part of the code you wrote for your winforms application if you designed it correctly.

  Posted to Enterprise Services Integration (Forum) by tomasr on 4/17/2006

• Re: Global server vatiable.

  There's no way you can share state between two arbitrary web applications without either having them pass data around in forms/query strings or having an external data repository such as a database or file. You really might want to rethink your design to avoid it. What are you trying to accomplish?

  Posted to Enterprise Services Integration (Forum) by tomasr on 4/17/2006

• Re: How can I export data to Excel by C# ?

  I've done this in the past for basic content by simply generating a Tab-delimited file (less problematic than dealing with CSV), and then having the ASP.NET app send that as the response to the client and use the Content-Disposition HTTP header to have the browser interpret it as an Excel file (since excel supports TSV files natively): Response.AddHeader("content-disposition", "attachment;filename=FileName.xls"); There are several articles out there on this, which a simple google search should reveal

  Posted to Enterprise Services Integration (Forum) by tomasr on 4/17/2006

• Re: calling external apps from ASP.Net using C#

  You pretty much would have to find a way to interact with said platform that enables remote execution and then either find clients/create clients for such protocols/tools to call from your ASP.NET code. Unix actually has had a fairly large number of said tools, but most of those are usually disabled/locked down in modern and well-managed systems for obvious security reasons (what you're asking is actually pretty insecure by itself). You could also choose to implement your own service on the remote

  Posted to Enterprise Services Integration (Forum) by tomasr on 4/17/2006