RemoteConfig in .NET Remoting?

brembot posted on Wednesday, November 29, 2006

Hello All,

I have setup my application in Windows 2003 Server IIS using .Net Remoting. I used NetRun (compiled using .NET Framework 2.0) to launch my application. As usual i rename my config file to remoteconfig file and enable the remoting statement. As i have notice in my internet temporary files. It doesn't download the remoteconfig file unlike the previous version of Csla (1.5). I know that the remoteconfig file handles the statement if you want to use .net remoting or not. Is my application uses .Net Remoting? Btw, I'm using Csla .NET 2.1.1.0

Any ideas? And also i'm having trouble in Window 2000 Server configuring my application.

Thanks

ajj3085 replied on Wednesday, November 29, 2006

Using NetRun doesn't mean you're using Remoting. It seems odd that your .remoteconfig file is not downloading, as I thought NetRun specifically downloaded the appropriate file.

Are you naming the file MyApp.exe.remoteconfig?

The config file is what will determine if you're using remoting or not.. but if its not downloading, you haven't even gotten that far yet.

Since you indicate you're using .Net 2.0 however, instead of NetRun I would recommend using ClickOnce installation. Its much more advanced than NoTouchDeployment.

Andy

brembot replied on Wednesday, November 29, 2006

ajj3085:
Using NetRun doesn't mean you're using Remoting. It seems odd that your .remoteconfig file is not downloading, as I thought NetRun specifically downloaded the appropriate file.

Are you naming the file MyApp.exe.remoteconfig?

Andy

Yes, I'm using you the one you mention. MyApp.exe.remoteconfig?

Thanks

glenntoy replied on Thursday, November 30, 2006

The reason why the App.exe.remoteconfig file is not downloading is that it can't be access when the NetRun application tries to setup the AppDomain.ConfigurationFile property. To solve this problem is to add a MIME type which the extension will be .remoteconfig and the mime type will be text/xml.

This can be done by invoking the properties in the IIS 6.0 and clicking the Mime Types button.

@ajj3085: Would it be possible to know where we can get good information about ClickOnce? Last time colleagues does the research there are also limitations in ClickOnce, correct me if I'm wrong especially dealing with registry and the only way to do that is a combination of MSI and ClickOnce which could also be complicated.

ajj3085 replied on Thursday, November 30, 2006

There's plenty of info if you google for clickonce. There are limitations, such as installs are per user only.

Modification of the registry may or may not be allowed depending on the trust level of the application.

You'd never have a combination of clickonce and msi, you'd choose one or the other. If you're doing heavy stuff, such as installing drivers (and possibly modification to HKLM) then ClickOnce isn't appropriate, but I've found it to be very capable for my Csla based application.

You might also want to rethink some things, like do you really need to use the registry for your application, or can your config file be used instead? One of the nice things is that user settings in the configuration file are kept when you release an update of your application, and so far its been very easy to deal with clickonce.

Click a link to install the application. Updates can be checked for before the application starts or on shutdown. You can require certain updates.

HTH
Andy