MarcF

Cambridge, UK

networkcomms.net

Age: 29

Cambridge University postgraduate researcher. Developer for the open source network library www.networkcomms.net.

7h
accepted Target .Net 4.0 when using Windows 8 / VS2012
2d
comment Target .Net 4.0 when using Windows 8 / VS2012
@HansPassant - You make a good point but I still need create assemblies for .net2.0+ systems. This is not a problem for .net2.0 and .net3.5 as those are made available in Windows 8, the problem was with .net4.0.
2d
comment Target .Net 4.0 when using Windows 8 / VS2012
@sixlettervariables - Yea, something does seem strange for my setup, no idea what. I have ultimate for both.
2d
comment Encrypt a file and send it through
If you would be happy to use a network library checkout this article networkcomms.net/using-encryption. I'm a developer for this library.
2d
awarded Supporter
2d
comment Target .Net 4.0 when using Windows 8 / VS2012
@sixlettervariables - I had VS2010 installed from the beginning, that didn't help.
2d
comment Target .Net 4.0 when using Windows 8 / VS2012
@KaushalDeSilva - Many thanks for the feedback but I managed to get it working by using solution 1 above, answer posted.
2d
answered Target .Net 4.0 when using Windows 8 / VS2012
2d
comment Target .Net 4.0 when using Windows 8 / VS2012
@KaushalDeSilva - Apologies, I should have mentioned that I have both VS2010 and VS2012 already installed. I may have a go at reinstalling.
2d
comment Target .Net 4.0 when using Windows 8 / VS2012
@Ronak - That directory does exist but only contains Microsoft.Office... and Microsoft.VisualStudio... assemblies.
2d
comment Target .Net 4.0 when using Windows 8 / VS2012
I do have the directory "C:\Program Files\Reference Assemblies\Microsoft\Framework\" but I only have v3.0, v3.5 in there.
2d
asked Target .Net 4.0 when using Windows 8 / VS2012
May
17
answered What to use? WCF or Sockets? in a C# program
May
16
answered Memory Fragmentation and Garbage Collection in network server apps
May
16
comment What C# class pattern should I use for mobile client / server objects
@Fyndor - You mention WCF as a possibility. There are also other network libraries available that can meet all of your concerns, particularly time to implement. Checkout code.google.com/p/lidgren-network-gen3 and networkcomms.net. I'm a developer for NetworkComms.Net.
May
15
comment Tcp Listener dies after about 50 hours
@500-InternalServerError - I am happily wrong but I read "about 50 hours like on weekends between listener and client" to mean that there is an established connection.
May
15
revised Tcp Listener dies after about 50 hours
added 1 characters in body
May
15
comment Tcp Listener dies after about 50 hours
@500-InternalServerError - I would suggest either on the underlying TCPListener socket or using a custom solution that sends packets manually once a connection has been established (via TcpListener.AcceptTcpClient).
May
15
answered Tcp Listener dies after about 50 hours
May
13
awarded Scholar
1 2 3 4 5