3 ms·

I'm still confused by the use of '.' to conflate namespaces & classes, and other things together. A separate character, like ':' or something else would've help

by malkia 13y ago

I'm still confused by the use of '.' to conflate namespaces & classes, and other things together. A separate character, like ':' or something else would've helped me :) Or GACs, or finding the right System.Data.SQLite module for your app - http://system.data.sqlite.org/index.html/doc/trunk/www/downloads.wiki http://system.data.sqlite.org/index.html/doc/trunk/www/downl... Or figuring out how exactly deployments/setups work - where things get put, etc. I don't know much about java - but it seems easier there - here is the .jar, simple .zip file, look at the manifest - and you are done.

alkonaut 13y ago
For package management I recommend you use NuGet and you should be good. No need to visit an sqlite website to download anything. Just type Install-Package System.Data.SQLite In your VS package manager console and you are good to go. Deployment/Setup is not really something C# or .NET cares about, there are many different forms of deployment. (IIS, Windows desktop, ClickOnce, Azure) and in each case you can do it in several different ways. I agree it's tricky to know what goes where sometimes, but it's more a problem with those targets than with how you build the application in question.
bruceboughton 13y ago
On the GAC: Never use the GAC -- except for platform libraries (System.*, etc.). Always deploy your dependency DLLs side-by-side with your code.
- malkia 13y ago
  I know that now, but there are still some .NET developers that I meet that think this is the way to go. Another problem with .NET is that there is a lot to learn, then unlearn - language, api, frameworks, deployment-wise. That by itself is not bad, if you are an active developer, but if you just given few times a year to fix this and that C# project, then it's a bit more painful. For example I have to upgrade 32-bit app using Antlr3 and system.data.sqlite (matching 3.7.0.1) to 64-bit, antlr3 newer version and system.data.sqlite (matching 3.8.2) - and after the upgrade there is significant slowdown, and some things do not work (possibly sqlite, but who knows for sure).

by malkia 13y ago

alkonaut 13y ago

For package management I recommend you use NuGet and you should be good. No need to visit an sqlite website to download anything. Just type Install-Package System.Data.SQLite In your VS package manager console and you are good to go. Deployment/Setup is not really something C# or .NET cares about, there are many different forms of deployment. (IIS, Windows desktop, ClickOnce, Azure) and in each case you can do it in several different ways. I agree it's tricky to know what goes where sometimes, but it's more a problem with those targets than with how you build the application in question.

bruceboughton 13y ago

On the GAC: Never use the GAC -- except for platform libraries (System.*, etc.). Always deploy your dependency DLLs side-by-side with your code.

malkia 13y ago
I know that now, but there are still some .NET developers that I meet that think this is the way to go. Another problem with .NET is that there is a lot to learn, then unlearn - language, api, frameworks, deployment-wise. That by itself is not bad, if you are an active developer, but if you just given few times a year to fix this and that C# project, then it's a bit more painful. For example I have to upgrade 32-bit app using Antlr3 and system.data.sqlite (matching 3.7.0.1) to 64-bit, antlr3 newer version and system.data.sqlite (matching 3.8.2) - and after the upgrade there is significant slowdown, and some things do not work (possibly sqlite, but who knows for sure).