NetOffice 1.7 Release

Developer
Oct 3, 2014 at 2:54 AM
Hi Sebastian,

Do you have any plans to create an official release of NetOffice v1.7?

Also could you give me some pointers on how are you currently generating all the assemblies targeting the different versions of the .NET Framework, so I can repeat the process?

I've been receiving a number of e-mails from people asking me to update the NuGet Packages, so if I make sure I generate the assemblies the right way, I can at least create pre-release versions of the packages as this repository gets updated.

Thanks,
Caio Proiete
Coordinator
Oct 4, 2014 at 4:44 AM
absolutly,

the problem is my notebook is completely wrecked and a lot of code are lost, so i still figure out to recover last state from different working copies :/

the tool i use to generate the code files is also available on codeplex: https://latebindingapi.codeplex.com (you need an active x control(tlbinf32.dll) to use this tool(given in the source code) this tool analyze the com type libs from office and save the informations as xml file.

what i do to generate a new release code is as follows.

1.) create 6 virgin virtual windows machines(2000,2002,2003,2007,2010, 2014), just office is installed.
2.) run the tool on the first machine, analyze, office core, excel, word, outlook, access and save the xml file.
3.) move the xml file to the second machine, load the xml file with tool and analyze the same office type libs in higher version, the new informations want be added with version informations. save the xml file and repeat this until the last machine.

you find a complete (compressed) xml file in the last source state: NetOffice 1.7.0.xml.rar
this is the last file i have generated the NO 1.7 preview

*Sebastian
Nov 1, 2014 at 11:11 AM
Hi,

would it be possible to even migrate the project to some better hosting (such sa Github), as this Subversion repository on Codeplex is super slow and I can't browser history of the project, or even do simple checkout of source code as I receive timeout many times.

This would allow better collaboration, and also way better support for generating NuGet packages.


Regards,
Jozef.