Hi Everyone,
Here is our Initial Plans in moving forward towards NPanday 2.0
*UAC REMOVAL
==============================================================================================================================
Class || Location
==============================================================================================================================
PathUtil || components/dotnet-core
Projectfactory || components/dotnet-dao-project
ConnectionRepository || components/dotnet-registry
ProjectDaoImpl || components/dotnet-dao-project
InstallerMojo || plugins/maven-install-plugin
ArtifactManagerMojo || plugins/maven-repository-plugin
RepositoryAssemblerMojo || plugins/maven-repository-plugin
RepositoryConverterForArtifactMojo || plugins/maven-repository-plugin
RepositoryRdfExporterMojo || plugins/maven-repository-plugin
Reference ||
dotnet/assemblies/NPanday.ProjectImporter/Engine
ResyncArtifactSnapshot ||
dotnet/assemblies/NPanday.VisualStudio.Addin
ArtifactRepository || dotnet/assemblies/NPanday.Artifact
PathUtil || dotnet/assemblies/NPanday.Artifact
==============================================================================================================================
UAC Removal Phases
==============================================================================================================================
1. We need to decide on how to "locate" an artifact/dll since dotnet requires
the <assemblyname>.dll convention and maven
uses the convention <assemblyname>-<version>.dll (this was one of the main
reasons for the creation of the uac)
- one of the things I can think up of atm is on the fly generation for the dll.
since its just a matter of stripping up the version in the dll. I don't know
how this will affect if there will be thousands of dll involve but I imagine
that the on the fly process should be negligble.
2. We need to determine the effects of the removal of the UAC implementation on
the classes mentioned above.
3. Reimplement the new method that we have decided on phase 1 basing from what
we have found out on phase 2
*VS 2010 SUPPORT
1. Determine the new project types that we need to add
2. Add the VS2010 Framework in the components and configurations of NPanday
These 2 Features that we have determined as top priority for NPanday 2.0 can be
worked with in parallel since the Removal of the UAC will be branched off from
the branch.
If ever I have missed something please feel free to speak up :D
Cheers,
--
Joe Ocaba
