I am aware of this thread .NET 6 how to add webservice reference but I am creating a VB.NET desktop app and when I go to Connected Services, I don't have the option of selecting Service References as in C#. Only Service Dependencies. Is there a workaround?
Related
My Prism 4.1 , Silverlight 5 Application have connectivity with oracle 11g via DevArt Oracle connector. My controls will be of Telerik
I've used EnitityFramwork 6 Database 1st Approach. Entitites & Context are in 1 c# project under Data module.
I'm unable to create (OpenRIA)RIA Domain Service library in my Prism project. It doesn't allow me to choose entitites from wizard. Means it doesn't show me the Entitites in wizard.
ITS OPENRIA with VS2013.
RIA Services Domain Services no longer exists as a wizard within Vs2013:
http://msmvps.com/blogs/deborahk/archive/2013/10/25/who-moved-my-cheese-ria-services.aspx
You instead have access to some NuGet packages, and the Open RIA Services project
Quick question
I am doing a Plural Sight tutorial on WCF and they are using the WCF Service Library (as opposed to application.)
When I go to Add new project there is no WCF Service Library. Not under any of the .NET versions.
I am using Visual Studio 2013 for Web Express.
Any one know how I can get it?
Thanks
You can find it under Templates WCF.
( Go to New Project->Installed-->Templates-->WCF)
I have a Class Library which contains a Linq to SQL object which is then connected to a database. I also have a WCF Service for other apps.
I now decided to use the same database in a Windows Phone 8 application, so connected to the Web Service which was fine. Some of the methods require a Customer object so i tried to import the DLL library with Linq to Sql and i got an error that it cant be imported (unable to add specified project reference. the reference must be a windows phone project).
I done a search on this and found some threads with similar issues but nothing to state what workarounds if any i could use to connect to a WCF Web service which accepts a Customer object as part of its method.
So is there a workaround? Does the service need to be recreated from scratch? Or any other alternatives.
About 2 years ago I worked on a WCF app, using VS 2008. I was using BasicHttpBinding. I got it onto a Windows 2003 Server R2, and then other projects came up, demanding attention. Now I'm trying to get back at it, only now I want to use VS 2010 to write the client side of the app (it's going to be a WPF app). I'm getting an error, but before I get into that I just want to know; can a .NET 4.0 app work with a WCF service written using .NET 3.5?
In theory, since you are using the Basic binding, you should be able to use any version of .Net to connect to your service. BasicHttpBinding offers the most compatibility across versions, so you're on the right track.
WPF Calling WCF Using a BasicHttpBinding
http://msdn.microsoft.com/en-us/library/bb943481(v=vs.90).aspx
I have writed a primitive wcf (vs 2010) service and created proxy files by svcutil. Later I created a mobile project on vs2008 and added proxy files on project but this error occured.
Error 1 The type or namespace name 'ServiceContractAttribute' does not exist in the namespace 'System.ServiceModel' (are you missing an assembly reference?) C:\Users\Abb\Documents\Visual Studio 2008\Projects\WCF\MobileService\MobileClient\Sample.cs
the proxy files runs well on console application (vs 2008) but there is errors on mobile.
System.ServiceModel doesnot support ServiceContractAttribute.
For mobile applications you shouldn’t use SvcUtil to generate proxies since this does not generate code compatible with the subset of WCF functionality available to the .NET Compact Framework on mobile devices.
Instead, you should use NetCFSvcUtil.exe. See this link for more information: Using NetCFSvcUtil.exe to interact with ServiceContracts