I am trying to integrate Blogengine into my existing .net website.
I found this page on stackoverflow, Is there a stable ASP.NET blogging control (designed for integration within existing site)?
step4 says, "4:Add the Blog Engine.core project in the Web Application. Build Blog Engine.core and add reference from your web project to “BlogEngine.Core.dll”.
What am I specifically supposed to do in this step?
Thank you!
Download the BlogEngine from http://blogengine.codeplex.com/releases. You should take the source version. It contains: BlogEngine.Core, BlogEngine.Net and BlogEngine.Tests.
You should take the project "BlogEngine.Core" and copy it to your solution, and reference it from the website where your blog is.
Related
I am looking for some guidance on the standard way of implementing plugins in D365 CE or what Microsoft recommends.
I generally follow this practice -
1. Have only 1 CRM Solution and one plug-in assembly (DLL) for all these plugin steps.
2. Have a separate ".cs" file for each plugin in this project.
3. Each plugin corresponds to specific functionality. So in case, we want to disable any functionality, it could be easily done without changing the code.
4. Have only 1 CRM Solution for all these plugins.
Looking forward to some expert guidance.
Thanks!
In this video former MVP Mitch Milam talks three plugin solution layout options. He recommends the approach you outline above, and that is the one I typically use.
I also generally use a Console app to test and debug plugins. For maximum flexibility, I often put all the business logic into a Visual Studio shared project. Then I reference that shared project from both the plugin project and the Console App.
While the Console app could reference a DLL, having the logic in a shared project easily allows me to also use the logic in a workflow project if I want. Ultimately, the shared project gives me the option run the code as a plugin, a workflow, or a Console app.
Here's an example:
The .Cmd project is the console app. The one with the double diamond icon is the shared project (which cannot be compiled on its own - it must be referenced by one or more compilable projects).
Could you someone please help me how to use XPages: A ClientSide State by Sven Hasselbach in Domino Designer.
The code provided on the GIT does not have site.xml to install in the domino Designer.
http://hasselba.ch/blog/?p=2115
You have to create your own OSGi Developement environment first, then you can create a new Plugin project and import the following files / folder:
/src
/META-INF
build.properties, plugin.xml
Now you can change the secret keys in
/src/ch/hasselba/xpagesclientstate/application/ClientStateManagerImpl.java
Next you have to create a Feature project, and an Update Site project and click on Build.
Then you have a site.xmlwhich can be imported into Designer & Domino server.
You need to create an update site project. Details are here:
https://wiki.eclipse.org/FAQ_How_do_I_create_an_update_site_(site.xml)%3F
For reference, see the answers to this question Deploying OSGi Servlet to Domino
I am developing a hybrid mobile application in dot net, i have created my own custom plugin using x_code and phone_gap . what are the ways to integrate my plugin to dot_net project.
This is an older question, but maybe this answer can help someone down the road.
This is the approach I have taken with DevExtreme to use a custom plugin and at the same time use the PhoneGap build process.
Upload your plugin to your GitHub Account.
Update your Config.xml
<gap:plugin name="your git hub package url" source="git"/>
(instead of name="" use spec="" and source="git")
NOTE: as of this post there is a bug in DevExtreme that if you attempt to look at Project Properties > PhoneGap Tab Studio will crash. DX is aware and they are suppose to fix it.
Build a custom template (this is the PhoneGap build portion)
Build your project.
I have written a servlet using the directions in this tutorial: http://www.slideshare.net/fiorep/domino-osgi-development slides 34 to 57. This worked well and was easy to debug when deployed via the pde.launch.ini. Now I want to work out how to deploy it to another server.
From what I can figure out, I think the preferred way is to create an OSGi bundle and deploy it via an updatesite.nsf. When I try to add a new local update site to the update site, it prompts me for a site.xml. This is where it falls apart for me - where does that file come from? Have I missed some steps?
When you want go to update site way, you first need to create a feature project, add the required plugins to this project.
Afterwards you need to create an Update site and the Feature project.
Finally click on build or build All.
Then there you have you have your update site somewhere on your local machine.
Point to the site.xml of this update site project when you want to import it in a update site Database.
For your OSGi project you have to create another project of type "Updatesite project". Add your OSGi project and all dependencies to that project and build it. This project will generate/contain the site.xml you need to deploy on Domino via the updatesite.nsf.
https://wiki.eclipse.org/FAQ_How_do_I_create_an_update_site_(site.xml)%3F
I have a solution with multiple projects and a website. On each project I have set up a pre build event to get the highest subversion revision number of the project (using SubWCRev) and then replace part of the AssemblyVersion with that revision number.
How do I achieve this on a website? As far as I can tell there is no pre build event and if I try to:
Add another project
Make the website dependant on the project
Use the pre build event for the project
The subversion revision number used to replace information in the website will be for the project not the website.
Any ideas?
One suggestion might be to use a Web Application project - rather than a Web Site project. Although this might not be entirely feasible in your case, depending on the amount of work required to essentially migrate the existing code-base.
See this question and its answers for more information: ASP.NET Web Site or ASP.NET Web Application?