Last post Apr 22, 2017 05:04 AM by kaushalparik27
Apr 21, 2017 04:27 PM|rogue1nib|LINK
What are the best practises when it comes to configuration informat for example I want to create a nuget of for a dll that calls an api url but of course I want that to be easy changed by the client using the nuget now of course you think of the config will
be in the web site or application that the user is using
string url =
So what would my best way to include the url so that the dll will be smart and retrieve in from the program web.config or app.config that they are using I no about the configuration manager is it just as simple as that?...
Apr 21, 2017 05:59 PM|kaushalparik27|LINK
I believe that usage of AppSettings key/value pair to store URL or any kind of settings that needed by dll is fair enough in this case, since you can access them via ConfigurationManager.AppSettings["SettingKeyName"] or alternatively you may use and include
any kind of setting json or xml file with nuget package and read values from it.
Apr 21, 2017 09:22 PM|rogue1nib|LINK
May I also ask how does one create a nuget package I saw a nugetmpackage manager floating about but it dont seem to work with visual studio community 2015 or 2017
Apr 22, 2017 05:04 AM|kaushalparik27|LINK
For that I suggest you refer to below articles, that covers similar topic on creating nuget packages:
Also, I prefer this way which seems quite easy:
Hot to create a NuGet package from the project after each build.