Hi there,
I'm trying to configure the remoting services and channels of an application using the app.config file in VS2005. It keeps giving me an error telling me that it...
Could not find schema information for the element 'application'
as well an error for every other child element under the <system.runtime.remoting> element. Here is the start of the configuration....
<configuration>
<!-- Configiration of the Remoting system -->
<system.runtime.remoting>
<application>
<channels>
<channel ref="tcp" port="6565">
<serverProviders>
<formatter ref="binary" typeFilterLevel="Full" />
....
Anyone know what's happening here
Remoting Configuration in VS2005
KlaasR
Myron_B
Okay last comment. I ran the Gacutil to add my assembly to the GAC and, oops, I'd forgotten to sign it. So, while doing other things and looking elsewhere for help I noticed that MSDN's own example for the <wellKnown> Element is as follows:
<wellknown
type="RemoteType, RemoteAssembly"
url="http://computername:8080/RemoteType.rem"
/>
My own read type="TestServer.TestService, TestServer" so I changed it to just "TestService, TestServer" and refreshed my browser (pointed to the wsdl page) and I got four empty textboxes!! Weird. I then changed my type parameter to a load of junk letters, refreshed and it was the same. So I changed my URL in the browser to http://localhost/TestService/TestJUNKServer.rem wsdl and still got four textboxes!
I put the real URL back again and refreshed and bing! There was my WSDL. I have no idea other than that the original problem was caused by a bad type= parameter and the rest of the behaviour is down to bugs, caching and things I don't understand in IIS/ASP.NET.
I hope the road to .Enlightenment gets smoother...
Nate F
Luke's application will have worked fine, assuming he didn't mess up any of the entries in his client.exe.config and server.exe.config files. I found this quite easy to do, and hard to spot. (I myself had somehow put the <channels> entry within the <client> entry for my client app, and in the <server> entry for my server app, and I had already triple-checked them both before spotting my mistake. An up-to-date schema would have caught this straight away.)
It's possible to create your own schema file (while editing your App.config, select Create Schema from the XML menu and it creates a schema file, then right-click inside and select View Code for the text version), but you need to make lots of edits to the resulting file (it marks everything as non-optional), and in fact you need to merge the results from your client.exe.config and server.exe.config. I just don't know enough about the schema file's structure, or indeed the details of system.runtime.remoting, to do this myself -- as easily as downloading a pre-made one, at any rate.
Supposedly you can put a separate schema file in C:\Program Files\Microsoft Visual Studio 8\Xml\Schemas and the IDE will see it, but that didn't seem to work for me (I even restarted the IDE); instead I had to edit the existing DotNetConfig.xsd file. But at the end of it all it was easiest just to undo everything and ignore the innocuous information messages (since the generated schema lead to more warnings and red twiddly underlined code).
ZychoFlow
Looks like your .Net framework installation did not complete cleanly. You could copy the xsd file from another machine where the installation went fine. There could be other incomplete files from the unclean install and so to be totally sure you can uninstall and reinstall the framework.
Mahesh[MSFT]
JoeAaaa
Tried uninstall .net 1.1 framework again and got the same problem so I unistalled VS2005 and re-installed it then ran the aspnet_regiis.exe -i and the problem has vanished.
MickR
Hi, I'm having an identical problem - it seems that others (Googling) have found missing schema data in the DotNetConfig.xsd file and have uploaded their own versions, unfortunately none contain the remoting stuff. From what I can tell, this only affects the intellisense in the XML editor
Thanks - Luke
Andrei Romanenko - MSFT
Hi all,
Sorry to have left like that, if it wasn't for the perpetual feeling that I'd be back on this the next day I would have returned to let people know that I had been placed on another project and had hence abandoned my foray into Remoting.
Anway, as baron said, it did work perfectly fine - well I say that, but it compiled and all would be fine if there wasn't a problem with ASP.NET not being able to find my class; System.Runtime.Remoting.RemotingException: Cannot load type 'TestServer.TestService, TestServer'.
According to written evidence, .NET should just find the assembly in the bin folder (if I have correctly entered its details in the type= parameter) so I will now put the assembly in the GAC to see if this is a problem with the .config file or something more sinister.
Thanks,
Luke
P.S. If anyone can cut and paste the missing section from the DotNetConfig.xsd file into this forum I'd be most grateful.
Emanuele Greco
After uninstalling and reinstalling the .Net Framework, I'm still having trouble with this issue. Any suggestions
Thanks.
Heinz_Richards
Hi all, I reinstalled both from my downloaded images (from MSDN) and the physical MSDN DVDs received in the post and neither seem to have solved the problem. I'm going to ignore it for now and see if any issues occur at runtime.
By-the-way, if you do reinstall and are using the Visual Studio 2005 Tools for the Microsoft Office System Runtime (vstor.exe) then you may need to install in the following order - you certainly did in 2003:
See http://msdn.microsoft.com/msdnmag/issues/03/09/MicrosoftOffice2003/
Cheers,
Luke
cope22
I was having this probelm too. The only thing I had done was uninstall and re-install the 1.1 framework. I have fixed the problem by unistalling vs 2005 and then re-installing it now all seems to be working ok.
Ricas
Just an update (I hate seeing other peoples threads dry up before the results), I've reinstalled .NET FW 2.0 and reinstalled, as well as VS2005, Office and other tools. I tried resintalling from the MSDN CD and the download I took from MSDN on its first day of release, in case there was something missing from the package - nothing has helped so far.
I still have yet to test if all is okay at runtime, I'm guessing it will but I'll let the foum know the actual outcome.
Thanks,
Luke
DanL_DeLorme
After a bit of investigation it looks like the DotNetConfig.xsd file doesn't have the System.Runtime.Remoting schema definitions!!
Anyone know where I can get an update
rkoski
Thank you for the response Mahesh.
Ricsi
Actually, forget it. I've decided that this whole .Net malarky really isn't worth it. I'm going back to flat HTML, no CSS, no remoting, no nothing. You lot are wasting your time. XML, XSL My idea of hell. MSDN and .Net are just a load of self-promoting Microsoft paraphernalia.
Luke