I am using Unity 2.0 with Silverlight 4 and RIA Services. Is xml configuration not supported in the web project of a Silverlight Business Application? The only way I can get the resolve method of the container to work is if I register my types at runtime vs design time in the xml config file.
Not at this time - Silverlight doesn't have System.Configuration, which is the library that runs the app.config / web.config file. It would take a LOT of duplicated code to get the existing config syntax working in Silverlight.
There was a project on Codeplex to provide a XAML-based configuration system for Silverlight apps using Unity.
Update: found it - http://sonicnet.codeplex.com - I guess I had a bad link when looking before.
Related
I need to upgrade an existing windows 8.1 Mobile app to work on windows 10 and started looking into this.
I have managed to port the code to UWP and it builds and runs the UWP app - so far so good.
However within the app there is a WCF project which is used to go get data and this isn't working.
I am currently getting this error Could not load file or assembly 'System.ServiceModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
Is it even possible for a UWP app to contain a WCF project and this will work?
In the VS2015 solution this all works but in VS2019 it doesn't work as in the ServiceFactory class cant even create an instance.
I have next to no experience of UWP or Windows 8.1 Mobile apps and any advice would be great.
Thanks
Gregor
Note that the WCF Client is actually available for .NET Core/.NET Standard! It's only the server-side part that is not available for .NET Core.
WCF Service: .NET Framework
WCF Client: .NET Standard based (works with .NET Core and .NET Framework)
In your case, if I understand you correctly, you want to call an existing service, which means you need the WCF client, and you can actually use that WCF client with .NET Core/.NET Standard 2.0 and so also with UWP.
Do the following:
Add a new .NET Standard Class Library project to your solution (this will replace the WCF client library that you have already in your solution)
In Solution Explorer, right click on Dependencies and select "Add Connected Service"
This will bring up a page within Visual Studio where you see the "Microsoft WCF Web Service Reference Provider":
Click on it, and the dialog below opens up:
In the dialog above, type in the URL of your service, and the dialog will generate the whole WCF client code for you and it will also add references for the required WCF NuGet packages.
Reference the .NET Standard 2.0 class library project from your UWP project and use it.
Note: WCF-Client in .NET Core does not support the configuration file entries known from .NET Framework projects. That means that the configuration is generated in the C# code.
I hope this helps,
Thomas
Can VS2012 build a proxy in a PCL project to consume a WCF service for SP2010? We add a reference (old school works everywhere else) but once we make calls, for instance GetListsCollectionAsync(), we get all sorts of errors. When we build the proxy, VS gives a warning:
Service proxy generation failed. Proxy requires type 'System.Xml.Linq.XElement' which is not supported in portable libraries
Has anyone successfully subscribed to a SharePoint WCF using a portable class library? The same stuff works fine in .net 4.5 class libraries and in metro libraries. Only portable ones give us this problem. We have win 7 and win 8 devices in the mix - so PCL would be a really good fit.
Got a conclusion here: We found a work around and the statement that this is a bug in VS2012 PCL projects still stands.
We created our proxy in a metro project and simply copied the reference.cs file over into the PCL project. It was a "what the heck - why not" last attempt of sorts, but it actually works. Even better, the calls are awaitable and come with response objects. Awesome!
Cheers,
Gregor
We have a collection of WCF Rest WebServices. Those WebServices are having configuration strings that are now hard coded as constants. We want to be able to change those configuration strings at runtime. A colleague of mine pointed me at the Configuration Service of the StockTrader sample application.
I installed the sample application and looked at working of the application. The Configuration Service is just a little part of the sample application. The documentation of the sample application contains a tutorial for the 'Visual Studio Configuration Service template', wich I followed. After that I found the 'Config Service Technical Guide' in the documentation folder of the sample application, wich contains a sort of action plan on page 12. The actionplan is just a summary what has to be implemented to use Configuration Service, not how it has to be implemented. Above the action plan the reader is referred to the 'Guide to Implementing the Configuration Service 5.0 for .NET Applications and Services'. Only thing after googling: The guide is nowhere to be found..
With the combination of the little actionplan in the technical guide, the comments in the code of the VS Template and the technical guide, I made a start to extract the Configuration Service and try to implement it in a new solution to test it. Now I am stuck with the implementation of the ConfigurationActionsBase. The implementation of the ConfigurationActionsBase persists the changes of the configuration to the database.
Does anyone know where the missing guide is(mentioned in the story
above)?
Does anyone know how to extract the configuration of magic
strings out of the StockTrader sample application?
Does anyone know an alternative solution for our scenario?
With Kind Regards,
What kind of project should I use ? I tried a WCF web site and then copied the directory into my DNN site and tried to goto the .svc file without success. Is DNN 6 for 3.5 only? Should I be running it as integrate and 4.0 in iis ?
The value for the 'compilerVersion' attribute in the provider options must be 'v4.0' or later if you are compiling for version 4.0 or later of the .NET Framework. To compile this Web application for version 3.5 or earlier of the .NET Framework, remove the 'targetFramework' attribute from the element of the Web.config file.
DNN has supported .NET 4 since DNN 5.4 (or thereabouts) and supports integrated mode in IIS (since early DNN 5.x).
It sounds like maybe you copied over the DNN web.config, which isn't going to work (there a lot of stuff in there that DNN needs to work correctly). Or, maybe you copied the WCF web.config into a subdirectory of the DNN site? If so, you probably just want to merge those web.config settings with the main config.
The main issue that I've had with getting WCF to work in DNN is making sure that WCF is installed with IIS (so it correctly handles the .svc extension).
I have an ASP.net web service sitting on a server, and I have verified that it works properly via a small test client app in VS.
I went to add it in MonoDevelop to my MT application, (Trying both the ASP.net 2.0 and WCF declarations). Inside the "Add Web Reference" wizard, it finds the web service fine. But when I go to reference it, the app doesn't know it exists.
I went to look at it, and it seems when adding it, the namespace it's assigning to it is the title of my solution (which has spaces in it), but the namespace for each of my .cs files within my app contains no spaces.
Web Service Namespace (that it wont let me change): Ultimate GameDay 2011
MT Application Namespace: UltimateGameday2011.
So I manually went into the reference.cs file and took out the spaces. The app classes then saw my web reference object, but it still won't allow me to access any of its members.
Any help would be greatly appreciated.
Check out the following link http://merbla.blogspot.com/2011/03/monotouch-with-json-using-aspnet-mvc.html
Its not a fix to your problem rather a method of creating web services that MonoTouch more easily works with. In my experience ASMX and WCF services have been problematic when consuming in a Monotouch app.
If all else fails, try using the Silverlight service utility located in your programs folder
e.g. C:\Program Files (x86)\Microsoft SDKs\Silverlight\v4.0\Tools\SlSvcUtil.exe