Is it possible? I couldn't find anything concerning this in the documentation. When I try to refresh cn1libs (which I downloaded over the CN1 preferences) in my cn1lib project it is stated that it's not relevant for this kind of project, although I would like to write a utility library based on other cn1libs.
There is no official support for dependency hierarchies in cn1libs because we don't want to create a "dependency hell". However, the extension manager does allow you to declare dependencies and you can use other cn1libs.
If you have a cn1lib you need to use you can just add it to the build classpath of the cn1lib you are currently building. In NetBeans this can be done from the GUI but can be done in other IDE's via the netbeans properties file. You can then use the other cn1lib, just make sure to include both cn1libs in the user project or you will get a dynamic link error.
See this https://www.codenameone.com/blog/tip-nest-cn1libs-cross-dependencies.html
Related
I'm using Eclipse with the Codename One Plugin.
Now I am starting a second project.
I would like to setup one or more "fragment" projects to avoid code duplication between projects. For example if I'm having a utility class for string concatenation I'd like to have this in a Utilities fragment project which then would be referenced by my projects.
What is the recommended way of doing this with Codename One?
For Codename One that's a cn1lib unfortunately at this time the Eclipse plugin is the only one that doesn't support the creation of a cn1lib (although it allows using them just fine).
Since a cn1lib is just an Ant project you can just download an existing project and put in your own code instead of what's there.
I am trying to publish a WPF application using the publish section in the project properties. When I attempt to specify application files (i.e. references) for the publish, I see lots of old dlls that were once in the project but were deleted later.
Is there a way to clean up this list so that it matches the references actually used in the project ?
It is not possible without extensions. However you can check this question for more details. There are also some extensions listed you could use.
I am using VS2010, When you create a new project, you can choose from ConsoleApplication, WindowsFormsApplication, WindowsService, etc. There's also Empty Project.
The empty project contains a reference folder without any references. What is the use of this Empty Project? Is it use for any test?
The “empty project” is used when you wish to create a project that does not have any files or reference automatically added to it.
Sometimes visual studio concept of being helpful is not what you want, and you just wish to be able to define a project to include only what you decide to put in it. This is not directly related to using a project for tests, but may be helpful when you are using a test framework that is not supported by any of the project templates.
i want to build a website in dnn 5. i have studied dnn5, its installation, starter-kit installation, built-in modules (both of Host and Admin), installing a custom module (from module extension), creating packages.
I had rather still some doubts left in my mind.
1.How should i progress if i need to built my custom module in some new website (& not in dotnetnuke.com website)
2.How is deployment done at client side? Is it done by creating packages or what, i dont know.please suggest some possible solution
3.I want to create a document module to satisfy my client requirements. This module is already built by dotnetnuke.com as an extra module. What should be done to include this module in my new website so that only my requirements could be reflected instead of creating the module entirely from scratch?
thanks
I'm not entirely sure about what you're looking to do, but I'll answer as much as I can.
I would suggest setting up a DotNetNuke website on your local machine, using the Source package. You can then create a new module (starting it either through the website itself, or by using a Visual Studio template). I strongly suggest using a Web Application Project for the module, keeping it in the website's DesktopModules folder (so that you're only dealing with the module's code, and don't have the entire website open in your project). Also, make sure you use the module and any other extension points to implement your functionality, rather than making changes to the actual DNN core code (since any changes to the core will make it that much more difficult to upgrade to newer versions of DNN).
I strongly suggest getting some automated packaging in place (the template that I linked to has a NAnt build script with it that you can use to package your module). It is so much easier to deploy modules as installable packages than trying to migrate individual files.
You can get the source version of the Documents module from its Codeplex project. It's licensed under the MIT license (like DNN itself), so you're free to use it as a starting point for your own module. Just download the source package and install it into your development site. The install will include all of the source and also includes a Visual Studio project that you can use. After installing, I would suggest that your first step be to rename the namespace (so that you're differentiated from the core module).
UPDATE
To deploy the website, I would suggest installing DNN on the server using the main DNN Install package. Then, once that is installed, you can install the module into the website using the package that you have created. A default installation of DNN will only have the Text/HTML module, in addition to administrative modules, so you shouldn't have very many extra, unused functionality present in the site.
Leave me a comment & update your question (or start a new question) if there's anything else you need to know.
It sounds like you are looking to use DotNetNuke as a development environment to write code that won't be deployed in a DotNetNuke site. While I love DNN, there's absolutely no reason to do this. Only use DNN for developing DNN stuff.
To address point #1, if the functionality you want is somewhere else you could use an IFRAME module. Check out: http://www.dotnetnuke.com/Community/Extensions-Forge/view/ProjectDetail/project/dnniframe.aspx
I have a Visual Studio Setup Project that I use to install a fairly simple WinForms application. At the end of the install I have a custom user interface page that shows a single check box which asks the user if they want to run the application. I've seen other installers do this quite often. But I cannot find a way to get the Setup Project to run an executable after the install finishes. An ideas?
NOTE: You cannot use Custom Actions because these are used as part of the install process, I want to run my installed application once the user presses the 'Close' button at the end of the install.
I believe this is one of the real limitations of the Visual Studio installation project. You need to be able to modify the last page of the installation UI but VS.NET does not give you a way to do this. You could modify the tables in the .MSI after it has been built but VS.NET would probably overwrite these changes each time it is built. You may be able to override the last page using a merge module that you include in the installation project. Either way you will need to become familiar with how the UI dialogs are authored in an .MSI and this is not trivial.
You may want to consider switching to a free script based installer or buy a commercial setup authoring application (just don't buy InstallShield for the love of Pete). Take a look at InstallAware (although I have not used it).
I've just found a very easy way which does not require external tools. You only have to add a class file to the main project and a custom action to the setup project.
http://www.codeproject.com/KB/install/Installation.aspx
You also can use custom actions
I've done this for internal apps by creating a VB Script harness that launches the setup executable, waits for it to close, and then launches the second program.
You could also accomplish this with a little more polish using a few Win API calls in a C executable.
You can use MSILAUNCH (though I've only got it to work with MSICREATE).
http://www.cornerhouse.ca/en/msi.html
I managed it by doing invoking the Main method the assembly using the following line:
(typeof(ClassWithinAssemblyToExecute)).Assembly.EntryPoint.Invoke(null, new Object[] {} )
you can do it by custom installer. just add installer class and there u will see many event like after install, before install. just hook up after install and from there run ur exe by process class. i would suggest u google to find more about custom installer.
here is one good link that might help u http://www.codeproject.com/Articles/19560/Launching-Your-Application-After-Install-using-Vis
thanks