-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dotnetcore #8
dotnetcore #8
Conversation
Well done Matt, you are just amazing, I'm really happy to work with you... |
I should also mention - one other thing I did in there. Because my local Redis instance is at a different IP. I abstracted that out into two helper files in the Demo and the tests. Because the two frameworks have different conventions for using config files they each maintain their own helper files to read the config respective to the environment. Example: public static string Redis => ConfigurationManager.AppSettings["redis"] While the same file in the dotnetcore project looks like this: static string _env;
static string Env => _env ?? (_env = Environment.GetEnvironmentVariable("env"));
static bool IsDevelopment => Env == "Dev";
public static IConfigurationRoot Configuration
{
get
{
var builder = new ConfigurationBuilder()
.AddJsonFile("appsettings.json", optional: true, reloadOnChange: true)
.AddJsonFile($"appsettings.{Env}.json", optional: true);
if (IsDevelopment) builder.AddUserSecrets();
builder.AddEnvironmentVariables();
return builder.Build();
}
}
public static string Redis => Configuration["redis"]; That's probably something that it should do anyway - and the nuget can provide it's own configuration settings file when installed - like NLog. So essentially, the Framework solutions are in the .Build folders and maintain their csproj file as well as any framework specific files and their packages.config. the non '.build' folders house the xproj files and their project.json files. |
Thank you very much Matt... |
Also i'm trying to create basic flows and drawings right now... |
Mind if I merge this pull request? It'll help me from dealing with conflicts to nuget updates and such. |
Of course keep going... On Thu, Oct 6, 2016, 21:38 Matt Krizanac [email protected] wrote:
|
I was looked forward for that one ;) On Thu, Oct 6, 2016, 21:47 Matt Krizanac [email protected] wrote:
|
#2 Rebuilt the solution like Nancy to allow linked code files across xproj and csproj. Had some merge conflicts with the nuget updates, but, they should be working correctly now.