There’s probably not an easy solution for this. You can create your own interface in a Portable Class Library with the same functionality. However that would be a different interface so other frameworks that use DataAnnotations (ASP.NET MVC and Entity Framework I think) wouldn’t use your version. To get around that problem, you could create … Read more
The differences will be in your .proj file. Having tried it myself you will have to do all of the following; Remove the <TargetFrameworkProfile> element Remove the <ProjectTypeGuids> element Change where you have #2 (below) for what I shown in #1 1. Regular class library <Import Project=”$(MSBuildToolsPath)\Microsoft.CSharp.targets” /> 2. Portable class library <Import Project=”$(MSBuildExtensionsPath32)\Microsoft\Portable\$(TargetFrameworkVersion)\Microsoft.Portable.CSharp.targets” />
I’ll answer your second question first: I have a library that targets .Net 2.0, .Net 4.5, and UWP. Targeting UWP required creating a new VS project and linking all the existing files, which is a huge pain. Now someone is telling me it doesn’t work for PCL, and from the sound of it I have … Read more
Update: We have fixed this in Visual Studio 2013. Portable libraries targeting Store (Windows 8.1) and .NET Framework 4.5.1 projects can now reference Timer. This is unfortunate case of where our implementation details are leaking to the user. When you target just .NET 4.5 and Windows Store apps, we actually cause you to build against … Read more
To implement the fix, first expand out the existing web.config compilation section that looks like this by default: <compilation debug=”true” targetFramework=”4.5″/> Once expanded, I then added the following new configuration XML as I was instructed: <assemblies> <add assembly=”System.Runtime, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a” /> </assemblies> The final web.config tags should look like this: <compilation debug=”true” targetFramework=”4.5″> <assemblies> … Read more