On 14/09/2010, at 4:31 PM, Josimpson Ocaba wrote: > Hi Everyone, > > Here is our Initial Plans in moving forward towards NPanday 2.0 > > *UAC REMOVAL
I think I've said this before, but I'd encourage you to split this into 2: 1) remove the UAC/PAB 2) remove the RDF store (dao-project) > > 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. When I made this work the first time, I copied it side-by-side in the local repository when needed. Not every piece of functionality needs this though, and those that do (like test) seem to be copying the files from UAC to target anyway. I'd suggest just copying them to a location in target when they are needed for running, and that this can be the responsibility of the plugin that needs it. To maintain compatibility, I would be very careful when making changes - if you identify code to remove, make sure it is being tested (ie, it passes the tests now, it fails a particular test when removed, and passes again when altered). This will be particularly important for the RDF repository removal because it has some sections of code like the GAC & COM reference resolution that won't be present in the Maven default resolution. I think you could break this up into a few smaller tasks. > > *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 What about VS 2010 support for the Addin? Have you reviewed the patch we have for this already? - Brett -- Brett Porter [email protected] http://brettporter.wordpress.com/
