Hey men,
First of it all:
Nice to see your ideas :) Please keep in your mind: NetOffice is a 1-men project. Its all me, for development, documentation, support. and i do this in my free time without any commercial reasons. obviously this have some drawbacks in time.
Currently i have problems submit any code because Codeplex has no working SVN bridge at moment. i have a lot of new code but i cannot commit them at moment.
The idea for an independent webstite is good but i'm not a webmaster btw. I need someone to do this for me.
Skip the toolbox? I was never realy happy with the toolbox but its easier as writing plugins/extensions for Visual Studio because Microsoft still hiding the documentation to programming Visual Studio. Only Microsoft (Gold?= Partners can buy these knowledge for a price a i dont know.
Moreover legacy is a basic idea of NetOffice aren't so ? dont care for the version means to support legacy as well - without issues. thats why i start NetOffice.
Wix is very good point! VSTO creates a setup/install project and NetOffice need to the same. But i see no other way as do that with the toolbox - do you see a better idea? ( i have one solution here in alpha state - but the problem is to refresh the project each time when the addin solution is-recompiled - i need an own vs project provider to do this - this is part of the visual studio internals)
at last: a NetOffice COM SHIM is currently available in a beta version. it works different to VSTO or addin-express. VSTO and addin-express need to install a runtime on the target deployment system. It means ONE! Shim install and run all the .net plugins which is created for. I didnt like the idea for xcopy deployement and create a different one. a C++ .dll which can parametrized from a .net plugin trough the registry(what VSTO does) or a config file. my problem with this solution is it is to complicated for beginners...
at the end:
Just writing Visual Studio extensions is not so easy as you think here. The setup project in the solution must do right the things in the corresponding build(each new build) from the target project. this is what a simple extension can not handle. you need an own code provider to do that. (Visual Studio is only a host application - that open xml files- the project guid in that file (for example csproj) loads the corresponding project provider- this project/code provider does all the low-level things NetOffice need - thats why i skip and create the toolbox)
in german we say "machste nix dran"
*Sebastian
First of it all:
Nice to see your ideas :) Please keep in your mind: NetOffice is a 1-men project. Its all me, for development, documentation, support. and i do this in my free time without any commercial reasons. obviously this have some drawbacks in time.
Currently i have problems submit any code because Codeplex has no working SVN bridge at moment. i have a lot of new code but i cannot commit them at moment.
The idea for an independent webstite is good but i'm not a webmaster btw. I need someone to do this for me.
Skip the toolbox? I was never realy happy with the toolbox but its easier as writing plugins/extensions for Visual Studio because Microsoft still hiding the documentation to programming Visual Studio. Only Microsoft (Gold?= Partners can buy these knowledge for a price a i dont know.
Moreover legacy is a basic idea of NetOffice aren't so ? dont care for the version means to support legacy as well - without issues. thats why i start NetOffice.
Wix is very good point! VSTO creates a setup/install project and NetOffice need to the same. But i see no other way as do that with the toolbox - do you see a better idea? ( i have one solution here in alpha state - but the problem is to refresh the project each time when the addin solution is-recompiled - i need an own vs project provider to do this - this is part of the visual studio internals)
at last: a NetOffice COM SHIM is currently available in a beta version. it works different to VSTO or addin-express. VSTO and addin-express need to install a runtime on the target deployment system. It means ONE! Shim install and run all the .net plugins which is created for. I didnt like the idea for xcopy deployement and create a different one. a C++ .dll which can parametrized from a .net plugin trough the registry(what VSTO does) or a config file. my problem with this solution is it is to complicated for beginners...
at the end:
Just writing Visual Studio extensions is not so easy as you think here. The setup project in the solution must do right the things in the corresponding build(each new build) from the target project. this is what a simple extension can not handle. you need an own code provider to do that. (Visual Studio is only a host application - that open xml files- the project guid in that file (for example csproj) loads the corresponding project provider- this project/code provider does all the low-level things NetOffice need - thats why i skip and create the toolbox)
in german we say "machste nix dran"
*Sebastian