These are chat archives for akkadotnet/akka.net

19th
Dec 2017
dferrell
@dferrell
Dec 19 2017 00:08
I have two applications that i am converting to akka.net and will be using clustering on both. Would it be best practice to give each cluster it's own system name and run separate lighthouse instances for each cluster system name or use the same system name and seed node config for both apps while using roles to isolate the two applications from each other?
Aaron Stannard
@Aaronontheweb
Dec 19 2017 03:10
ok. one more question then: why I can't build the solution on mac? there is still this .nuget folder in the solution which is empty, but in the solution file it expects some files to be there
you should be able to
we're able to build it from the commandline at least on both Windows and Linux
are you trying to open it in an emulated VS instance?
Maxim Cherednik
@maxcherednik
Dec 19 2017 07:33
nope, just vs 2017 for mac
Bart de Boer
@boekabart
Dec 19 2017 08:10
vs2017 for mac, afaik, is specifically targeted at x-platform app development
Maxim Cherednik
@maxcherednik
Dec 19 2017 08:16
I can do other projects there...
Maxim Cherednik
@maxcherednik
Dec 19 2017 08:28
image.png
These ones are not in the repo and they are not used. Strangely, vs2017 for windows does not show these files are gone. Only if I try to open them, it says can't find it.
Jonas
@jonasro_twitter
Dec 19 2017 09:37
Are there anything built in to akka.IO and tcp with regards to keepalive messages or checking whether the server is alive? How do people usually implement handling for half-open connections?
Diego Liñan
@diegolinan
Dec 19 2017 13:02
Hello! I'm having an issue I can't find a solution for anywhere. I'm trying to create several App.config files for my solution that can potentially contain different HOCON configurations depending on which environment I'm deploying to. I would like to do transforms as with any other field on the appSettings area but it seems to be impossible. Has anyone done this before? Samples? Thanks!!
Diego Liñan
@diegolinan
Dec 19 2017 14:49
According to the docs (which sometimes lack on examples): "Parsing HOCON from a string is handy for small configuration sections, but what if you want to be able to take advantage of Configuration Transforms for App.config and Web.config and all of the other nice tools we have in the System.Configuration namespace?"
So, how do we do transforms on the HOCON or how we can user different config files with different HOCON Configurations...
Maxim Cherednik
@maxcherednik
Dec 19 2017 20:24

@Aaronontheweb

image.png

I think we don't this anymore, I will create a pull request for this

Aaron Stannard
@Aaronontheweb
Dec 19 2017 20:24
ah I see
yeah I don't think we need those
@diegolinan people have used App.config transformations to replace the entire HOCON section
seen it done
don't have an example on-hand though
Maxim Cherednik
@maxcherednik
Dec 19 2017 20:25
plus a couple of projects have "version=" with a small 'v' it's actually case sensitive
Diego Liñan
@diegolinan
Dec 19 2017 20:25
@Aaronontheweb Damn... I was thinking the same but just can't get it done... Will continue researching
Maxim Cherednik
@maxcherednik
Dec 19 2017 20:26
btw why do we target several platforms rather than just a standard ?
452;netstandard1... something
Maxim Cherednik
@maxcherednik
Dec 19 2017 20:45
@Aaronontheweb which version of the cproj we are aiming
I see this kind of lines: <PackageReference Include="Microsoft.NET.Test.Sdk" Version="$(TestSdkVersion)" />
and it seems that this is an old approach
my vs, which is vs 2017 is crying about this
plus the build script is not understanding this either
@Horusiath
Maxim Cherednik
@maxcherednik
Dec 19 2017 20:55
I kinda do not understand how it works for you. I took the latest dev and it's not building from the script, cause there are some really missing things in some project files. Do I take the wrong branch? Does any of you guys work on mac?
Bart de Boer
@boekabart
Dec 19 2017 21:17

btw why do we target several platforms rather than just a standard ?

I actually discovered today, that when you have a netstandard (e.g. 1.3) only library, you can't reference that in a net462 (in our case, one also referencing Topshelf) library.

Or at least - I couldn't get it to work. That might be the reason?
Bartosz Sypytkowski
@Horusiath
Dec 19 2017 21:20
@maxcherednik If I remember correctly we got some conditional compilations that are available only in full .NET framework
also the default branch is /dev and this is where we put all the PR
Maxim Cherednik
@maxcherednik
Dec 19 2017 21:25
ok. it seems I found few misconfigurations
somehow they are not visible in win 10 vs2017
but they do exist
for example:
Package System.Diagnostics.TraceSource 4.3.0 is not compatible with net452 (.NETFramework,Version=v4.5.2). Package System.Diagnostics.TraceSource 4.3.0 supports:
  - monoandroid10 (MonoAndroid,Version=v1.0)
  - monotouch10 (MonoTouch,Version=v1.0)
  - net46 (.NETFramework,Version=v4.6)
  - netstandard1.3 (.NETStandard,Version=v1.3)
  - xamarinios10 (Xamarin.iOS,Version=v1.0)
  - xamarinmac20 (Xamarin.Mac,Version=v2.0)
  - xamarintvos10 (Xamarin.TVOS,Version=v1.0)
  - xamarinwatchos10 (Xamarin.WatchOS,Version=v1.0)
this is what I get as a warning in vs 2017 under mac os
but I don't see this warning when I run with the script
Either it's swallowed
Maxim Cherednik
@maxcherednik
Dec 19 2017 21:31
or it does something under the hood
Maxim Cherednik
@maxcherednik
Dec 19 2017 22:00
@Aaronontheweb btw, if the project is not supposed to be developed under mac os, maybe we should mention it somewhere ?
Bartosz Sypytkowski
@Horusiath
Dec 19 2017 22:07
@maxcherednik I guess we can assume that Mac OS support is simply best effort. It's hard to tell what may not work for the specific environment if there is no feedback from the people using it there... well at least up to now ;)
Maxim Cherednik
@maxcherednik
Dec 19 2017 22:07
:)
Bartosz Sypytkowski
@Horusiath
Dec 19 2017 22:08
your input here is valuable
Maxim Cherednik
@maxcherednik
Dec 19 2017 22:08
ok got it
still the recent pull request #3217, I think it's valid not only for the mac os
when you have time could you please have look
Package System.Diagnostics.TraceSource 4.3.0 is not compatible with net452 (.NETFramework,Version=v4.5.2). Package System.Diagnostics.TraceSource 4.3.0 supports:
  - monoandroid10 (MonoAndroid,Version=v1.0)
  - monotouch10 (MonoTouch,Version=v1.0)
  - net46 (.NETFramework,Version=v4.6)
  - netstandard1.3 (.NETStandard,Version=v1.3)
  - xamarinios10 (Xamarin.iOS,Version=v1.0)
  - xamarinmac20 (Xamarin.Mac,Version=v2.0)
  - xamarintvos10 (Xamarin.TVOS,Version=v1.0)
  - xamarinwatchos10 (Xamarin.WatchOS,Version=v1.0)
Regarding this one. I will try to run on windows, so that to figure out if:
  1. it's using the same version
  2. and why it's working there
Bartosz Sypytkowski
@Horusiath
Dec 19 2017 22:24
to be honest I'm not the best person to solve .NET standard compatibility problems - @alexvaluyskiy did a tremendous work on this field (he did most job on porting akka.net to .net standard)
Maxim Cherednik
@maxcherednik
Dec 19 2017 22:25
ok, maybe he can enlighten us here