Visual Studio and SvcUtil can be used to create proxy code for integration with the service. There were problems in VS 2010 and earlier if you wanted to maintain a link library for different levels. This forced several workarounds to solve the problem of equivalence in types of data contracts and the inability to correctly use local types.
Link URL for Problem: Generating WCF Client Code - Problem with "Reuse Types from Reference Assemblies"
I am using Visual Studio 2012, ASP.NET 4.5, C # code
My question is: "Was there reuse of assembly types in VS 2012?" I am porting some code now, but I am also worried that this error may occupy his head. I can run test cases, but that would be faster if someone had the answer. In my experience, if you cannot find the answer online (googled it and the get get 2011 - the problem still exists), that the fix may not be in place.
My goal. Let my future development team reuse the same type of library in enterprise and .Net application tiers. [Presentation (website, mobile application level - server side ...), domain (services, business logic level), Data Access Level)]. I would like to ensure code uniformity and reuse. The code will be “loosely coupled” at each level, but types will be provided through a test build. Equally, I want the code to support external integration for third parties in the future. Thus, I need to build all types of proxies from types decorated with DataContractAttribute for external services and support reference types for server-side applications.
? ? .