All I could get about DNN ListX control is the following link
http://dnnuke.blogspot.in/2007/09/using-listx-component-to-create.html
The link provides information about the configuration but where can I see all those screens to edit the query and contentPane items?
Any more information about ListX is most appreciated.
You probably are having trouble locating information because ListX is an old and unsupported module. You probably should look for an alternative. Two choices include 2sxc and Open Content. Both are free and open source.
After doing some research on ListX I found that Bi4ce ListsX was replaced by OWS (Open Web Studio).
I installed OWS on my website and upgraded my ListX to OWS. After upgrading I could easily locate the settings and perform all types of configuration I needed.
Here are many useful resources to learn about OWS.
Related
I am preparing a WPF app to be released, I have about 5 modules (Class Libraries) along with the main app (Windows Application), should I change all the modules and the application build configurations from Debug mode to Release mode? or is it enough to only change the Main App build configuration mode to Release?
Toolbar
You can refer to the toolbar and select specific configuration for the current solution. It will automatically change building configuration for the all projects included in the solution itself (in spite of any dependencies between projects).
In case if you cant see the configuration combobox in toolbar, try to add it using the Standard Toolbar Options button.
Configuration Manager
Used for detailed building configuration management. Change configuration and platform options here both for one single project or the whole solution.
Menu bar/Build/Configuration Manager
Security
Unfortunately or not, but there is no solution to ensure the complete security of the application. We can combine a bunch of different techniques, but thats still not secure enough.
Please refer to first, second answers of this question to get details.
Change all to Release with the main app as well and build. There is no reason to have debug code, for size and security, in released software.
I have a project that was last run earlier this year. I've installed latest netbean with plugin but get the following when I start the app.
java.io.UTFDataFormatException: malformed input around byte 200
at java.io.DataInputStream.readUTF(DataInputStream.java:656)
at java.io.DataInputStream.readUTF(DataInputStream.java:564)
at com.codename1.ui.util.Resources.loadTheme(Resources.java:1270)
at com.codename1.ui.util.Resources.openFileImpl(Resources.java:303)
at com.codename1.ui.util.Resources.openFile(Resources.java:269)
at com.codename1.ui.util.Resources.<init>(Resources.java:189)
at com.codename1.ui.util.Resources.open(Resources.java:768)
at com.codename1.ui.util.Resources.open(Resources.java:688)
at com.codename1.impl.javase.JavaSEPort$4.run(JavaSEPort.java:1720)
at com.codename1.ui.Display.processSerialCalls(Display.java:1056)
at com.codename1.ui.Display.mainEDTLoop(Display.java:873)
at com.codename1.ui.RunnableWrapper.run(RunnableWrapper.java:120)
at com.codename1.impl.CodenameOneThread.run(CodenameOneThread.java:176)
I did create a sample app that worked and noticed that the properties tab shows it as a Gui Builder Project. My older project does not show this. I have tried comparing the properties but I do not see what is determining this.
I also copied the theme and the sample code into my project, used that as the main class. The problem still persists.
Any help would be appreciated.
Thank you
Sam
We updated the format of the resource files so newer skin updates might collide with this project. If you use Update Client Libs it should work fine.
However, this change might also cause issues with newer skins if you are using versioned builds. Since the skin includes the native device theme within and we updated the theme file builtin the skin. You can understand our motivation for this change by looking at the before/after screenshots in our 3.8 release announcement.
As a workaround for that problem you can switch a skin and download an older version of a device skin from our skins project. You can then add that skin manually and use that.
I have built one windows forms application and I published for client installation. While installing the setup file, it should ask the user to select the installation directory path; instead, it's installing in default path as below :
C:\Users\Mysys_t\AppData\Local\Apps\2.0\434YBBVC.Z2H\TNYPR09N.1JZ
Is there any settings to do this, so that, while installing, user is able to select the installation directory?
In general, the answer is no. See a related MSDN forums discussion among other online references that explains why: ClickOnce was designed to automatically manage installation directories to prevent deployment collisions.
Now...the referenced MSDN forums discussion also links to one way to possibly work around this. Certainly anything is possible with some ingenuity and work (e.g. publishing a setup wrapper with ClickOnce to leverage ClickOnce's auto updates but use indirection to control where your actual app ultimately gets installed); but this is not possible using ClickOnce "straightforwardly".
this can be achieved by
Creating an MSI Package for C# Windows Application Using a Visual Studio Setup Project
pls follow the link below :
http://www.c-sharpcorner.com/UploadFile/1492b1/creating-an-msi-package-for-C-Sharp-windows-application-using-a-v/
I have a WPF solution (C# & VS 2012) that calls an external EXE. I've added a reference to the external EXE in the main (Dashboard) project.
The solution is getting packaged into the ClickOnce package and published. The issue I'm running into is that the CONFIG file for the external EXE is not getting picked up in the ClickOnce package.
When I open the Application Files window on the Publish tab in VS2012 it shows the external EXE.
But the configuration file for external EXE is not listed, even with the "Show All Files" checkbox selected.
So my question is:
Is there a way to either manually add a config file to the ClickOnce deploy package or somehow coerce it to see the config file?
This is my first ClickOnce deployment project so I'm struggling a little here and any assistance would be appreciated!
Thanks!
UPDATE/SOLUTION FOUND:
After much web surfing I found an fix for this issue. Here's the posting on MSDN that helped me MSDN: ClickOnce and External config. This at least solved the issue for me in the short term. As noted in the MSDN post it can cause issues down the road if the external config changes frequently.
UPDATE/SOLUTION FOUND: After much web surfing I found an fix for this issue. Here's the posting on MSDN that helped me MSDN: ClickOnce and External config files. This at least solved the issue for me in the short term. As noted in the MSDN post it can cause issues down the road if the external config changes frequently.
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