Great addition that was desperately needed for multi-platform. It's not perfect yet, but is a great stride forward to delivering a cross-platform runtime. Please keep adding namespaces such as the new ones introduced in .NET 4 and 4.5. Thank you!
It is great tool, but as the other said, please add the namespace System.XML.Linq and System.ComponentModel.DataAnnotations.dll since they are available in new .net framework. http://support.microsoft.com/kb/2600211
This is an extremely useful tool. It has helped me a lot when designing data models for projects where the target platforms have not yet been finalized and where leaving open the option to add additional platforms in the future is desirable.
You changed the System.Threading.Thread class. Why?
I was using the Thread class and it was running well, why would you remove it? Can you please explain the reasons behind those desicions? Will you put it back in? Should we just use the Release Candidate version instead?
var thread = new System.Threading.Thread(new System.Threading.ThreadStart(() =>
Please let me know why a good thing would be removed.
We needed to remove explictly thread creation for a reason that we're not ready to discuss yet (ask me again in 3 months). We didn't want to remove it, but a late design requirement forced our hand. :(
While the RC will build assemblies that work today, it will not build assemblies that will run on future platforms.
A replacement for what you are doing is simply to call ThreadPool.QueueUserWorkItem. Sorry for any inconvenience.
I will ask you after the Build conference. We will work around it for now.
We're pretty excited about the posibilities that Windows 8 will bring. Will there be a portable API for thread management and work distribution released later on?
I really hope that the good outweighs the bad on this one. It really seems like it crippled the entire project in my opinion.
1. >> A replacement for what you are doing is simply to call ThreadPool.QueueUserWorkItem.
I would like to convey some garantee with sequance of calls; but using ThreadPool.QueueUserWorkItem is out of question. Having a "Thread" for _long_ running operation would be beneficial.
2. Are we going to see Syste.Net.WebClient in PCL? (MSDN Lib is out of date)
Thanks Mike for the feedback. Now that build has been annnounced, I can mention that reason explicit Thread control was removed was because it's not supported on Windows 8 Metro style apps. WebClient is the same. You can provide feedback around what that surface area over on the Windows 8 forums: http://social.msdn.microsoft.com/Forums/en-us/category/windowsapps.
StreamReader.Close will not be re-added. It's replacement is Dispose (or a "using" block). We've deprecated all the different methods that represent the same concept as Dispose to try and reduce confusion. With regards to IEnumerable<char> on String, what are you using it for? Do you have a method that takes IEnumerable<char>? Or are you using the Linq methods on it?
attempting to port Lucene 4 using PLT on a new experimental branch to see in hopes PLT would be a good fit.
There are a few places where the code accepts ICharSequence in Java. The closest thing that accommodates this in .NET is IEnumerable<char>. Both strings and char or objects that implement ICharSquence that are used through out the code base. So essentially it both accepts IEnumerable<char> in method signatures then using linq methods that simulate ICharSquence methods i.e ElementAt for CharAt.
Also has there been any testing or guidance on installing/setting up PLT for build scenarios?
Thanks for the feedback. RE The build scenario, you can install PLIB tools on a build server by passing the /buildmachine to the setup. This will enable you to install on a machine without Visual Studio installed.
My portable library project has reference to System.Xml.
When I added reference to the project to aspnet website and when I deployed it to II6 I got following error:
Could not load file or assembly 'System.Xml, Version=220.127.116.11, Culture=neutral, PublicKeyToken=7cec85d7bea7798e, Retargetable=Yes' or one of its dependencies. The given assembly name or codebase was invalid. (Exception from HRESULT: 0x80131047)
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
I tried configure assembly binding in web.config, but I can't make it working. More details here: http://forums.asp.net/t/1678467.aspx/1?Could+not+load+file+or+assembly+when+referencing+PortableLibrary
We'll have clearer docs around this when we release, however, you need to have Update for Microsoft .NET Framework (KB2468871) installed on the web server. You will also need to remove the the binding redirect - this will actually have the reverse effect of disabling the feature. :)
Hi. I'm still having this issue after removing the Library, reinstalling VS 2010 SP1 and then putting the library back on. I think there's something stuck in my solution somewhere. Any ideas where I should look?
David m. Kean - the link you supplied doesn't work. Could you let me know the correct one?
I posted this earlier but did not get a response...
When trying to deploy I select this prerequisite under the setup project properties: Microsoft .NET Framework 4 Client Profile (x86 and x64) and Update for .NET Framework 4 (KB2468871) But when I build the project I get this error and the final package does not strap the updates. "The version of the .NET Framework launch condition '.NET Framework 4 Client Profile' does not match the selected .NET Framework bootstrapper package. Update the .NET Framework launch condition to match the version of the .NET Framework selected in the Prerequisites Dialog Box." Can you provide some help?
You need to remove the '.NET Framework' launch condition or change it to 'Any' under the View -> Launch Conditions designer. Unfortunately, we couldn't get the update to be listed as one of the launch conditions. This won't affect the pre-install of .NET Framework if you run Setup.exe.
No, if the setup.exe is run, then these updates will still be pre-installed. What it means is that if someone double-clicks on the msi instead of the setup.exe to install then they won't be told to install the framework and/or updates.
(I'm a powershell dunce still, but ran across this today while writing some deploy scripts. It may be a powershell issue, but still thought it may be of interest)
$assem = [Reflection.Assembly]::LoadFrom(<path-to-net4-assembly>)
However, if I substitute <path-to-net4-assembly> with <path-to-portable-assembly>, the GetCustomAttributes($false) fails with: "Could not load file or assembly 'System.Core, Version=18.104.22.168, Culture=neutral, PublicKeyToken=7cec85d7bea7798e, Retargetable=Yes' or one of its dependencies...".
Interestingly (oddly?), $assem.GetName() succeeds with either a net4 or portable assembly. Also, in the MSDN docs, GetCustomAttributes is marked as portable.
PS: Is there a more "official" way to give feedback than the Q and A area?
This is strange, I'm not an expert on PowerShell's environment, so can you try and few things and tell me the results:
1) Could verify that http://support.microsoft.com/kb/2468871 is installed on the box?
2) If so, can you try the same thing in a .NET Framework 4.0 Console application and see if that works?
3) Can you run the equivalent of Console.WriteLine(Environment.Version) in PowerShell and tell me the results?
If you would like to track this issue, feel free to file a bug over on http://connect.microsoft.com/VisualStudio.
Whoa -- the KB update did it. Nice catch!
I'm really excited about this project, especially with the new WinRT. I'm hoping to be able to use it to define service definitions across multiple platforms. Looking forward to see where it goes!
If my Portable Library (PL) has a reference to a System.Net object, the consuming .net4 library won't compile unless I add a reference to the System.Net assembly (which doesn't actually contain any of the objects I'm using).
For example, I have an interface that returns a WebRequest in my PL. I implement the interface in my .net4 library, add a "using System.Net;", and everything looks good, but compilation fails. If I add a reference to the .net4 System.Net assmebly (which doesn't contain WebRequest...), then everything compiles.
I can provide an example solution if needed (though I don't see anyway to attach a file to this thread).
David, thanks for trying it out.
What you are seeing is actually due to the how we make Portable Libraries work in .NET 4.0. I actually cover this exact scenario in our Channel 9 interview: http://channel9.msdn.com/Shows/Going+Deep/NET-45-David-Kean-and-Marcea-Trofin-Portable-Libraries. See minute 18:20. We're trying to make this scenario a little better in Dev11.
I have a persistence agnostic "entities" Library that only includes the entities as classes and their properties. These are the classes I serialize over a RESTful protocol.
I was really hoping that I could now add basic things like StringLength, Required etc to the library, and keep it portable on server and client.
It seems System.ComponentModel.DataAnnotations is not supported in a Silverlight/.Net4 portable library?
Please tell me it aint so - I just assumed this would be natural for people to want to do :-)
OK, fair enough (as long as it gets done in a sooner update rather than later ha ha ha).
So, pragmatically speaking, what are my options? 2 copies of each entity class file (they arent big, but I got a lot of 'em :-)). Is there a better way? with good 'ol #IF?
This really bums me out since for me, this is probably the biggest reason to use portable libraries- Domain Driven Design ya know :-)
Ive thought more about how best to workaround this: does this make sense?
Have all of the entity .cs files in a directory. Each .cs file has #IF SILVERLIGHT around the data annotations, so they are only specified for the silverlight build.
Have 2 projects, each with links to the entity files- one project for .Net4 server side, and one project for silverlight (the silverlight project defines SILVERLIGHT).
Build both projects.
Upside is it is "single source", downside is all the #IF stuff.
Is there a better way? I definitely dont want to have 2 copies of the .cs files.
Thank you so much for reading -
Hi, I have the same issue, I am trying to leverage Dto classes that I have used for a WPF/WCF application and I was hoping to be able to use the DataAnotations and the IDataErrorInfo in my Dtos. When I select .Net4 and SL, they are not available. Strange when SL fully supports both.
Thanks. Types and assemblies are not automatically sharable between platforms, hence why these are not available. We need to do work on our side to make them sharable; we need to verify that they can be consumed in a platform-agnostic way, write tests, fix any incompatibilities and add them to our reference assemblies. This takes time and work, so we focus on what we deem to be the more important APIs first.
Sometimes I need a value different from null, that is where DBNull can fit in.
I know I can define my own type to do it, but that's what DBNull supposed to be.
Also since every currently supported target framework uses DBNull how do I use my own define type that to interop with other .NET components that know what to do with DBNull?
I can't even define conversion operator for DBNull since it's unknown to PTL.
And you say it's not supported in Windows 8 Metro style applications, but it is supported in all target frameworks I can choose now, if you don't want it appears in a type library targeting Windows 8 Metro style application, why not make an additional option targeting it?
BTW, can Windows 8 Metro style applications interop with Metro style IE? If it happens, what do you use to represent a JScript "null" in CLR?
When trying to deploy I select this prerequisite under the setup project properties:
Microsoft .NET Framework 4 Client Profile (x86 and x64) and Update for .NET Framework 4 (KB2468871)
But when I build the project I get this error and the final package does not strap the updates.
"The version of the .NET Framework launch condition '.NET Framework 4 Client Profile' does not match the selected .NET Framework bootstrapper package. Update the .NET Framework launch condition to match the version of the .NET Framework selected in the Prerequisites Dialog Box."
Can you provide some help?
Can you guys please include Code Contracts? It seems like the better way to go than to constantly do:
if (myParam == null) throw new ArgumentException("...");
System.Diagnostics is already a supported namespace, so just throw the System.Diagnostics.Contracts namespace in there :)
Thanks for trying it out. Code Contracts is on our backlog for a future version. SerializableAttribute was removed deliberately because it has been replaced in favor of DataContractAttribute. COM isn't supported, hence why ComVisibleAttribute isn't available. What are your usages of these attributes? Do you have them because you actually need them, or are you just trying to convert existing code over to it?
I had an existing ReadOnlyDictionary class that I wrote. I modeled it heavily on the ReadOnlyCollection and I followed the "Microsoft All" Code Analysis ruleset. That lead to me adding the "ComVisible(false)" attribute and Code Analysis suggested I should add the Serializable attribute to my class. I'm not sure if DataContract is the right way to go here, but if it is then I should probably look at CollectionDataContract I assume (that way I can provide a KeyName and an ItemName)?