Facilitiate contribution
Posted: March 2nd, 2015, 11:48 pm
Currently is is very difficult to contribute back to phalanger on GitHub because of the lack of documentation on the initial setup plus:
1. .csproj files are under Visual Studio source control. The first problem anyone faces is that these project files will simply not open. VS Source control should be completely removed from the .csproj files in GitHUB.
2. Deploymnent commands are failing on VS2103 (don't know about other versions). But, why rely on GAC to deploy?
During development the GAC assemblies get blocked and updating them is a mess. Using direct path to DLL from web.config is better and more reliable. Personally, I'd remove deployment commands except copying the dll's to the "\Phalanger\Deployment\Debug" directory. The web appliaations can reference the dll's in that directory directly.
Greetings!
1. .csproj files are under Visual Studio source control. The first problem anyone faces is that these project files will simply not open. VS Source control should be completely removed from the .csproj files in GitHUB.
2. Deploymnent commands are failing on VS2103 (don't know about other versions). But, why rely on GAC to deploy?
During development the GAC assemblies get blocked and updating them is a mess. Using direct path to DLL from web.config is better and more reliable. Personally, I'd remove deployment commands except copying the dll's to the "\Phalanger\Deployment\Debug" directory. The web appliaations can reference the dll's in that directory directly.
Greetings!