I have installed CrystalReports in a project using VS2019. I want to host this on a shared webserver. I do not have access to install CrystalReportsRuntime on server. What are my options to achieve the same?
I have tried copying all files from Nuget package references but no luck.
Please advise
As per the comments mentioned above, I thought of writing it as answer. One cannot run CrystalReports without the runtime being installed on server. So, unless the hosting company installs the runtime, CR wont run on shared hosting. You can chekck this on Authorized SAP Community Link here.
Related
I want to install PLESK on our VPS. We are already using this VPS is in production and the hosting company recommend to reinstall the server first, then install Plesk and then republish the data.
However, I can find no information anywhere if it is risky to install Plesk on an already running productive VPS without reinstalling it before.
The problem is: A former coder has produced code that we use on daily basis, and I don't know if he made any changes on the server, which would have gone when performing the prior reinstall.
Thank you for your help.
An official Software Requirements document for Plesk in Windows, tells that "We strongly recommend that you install Plesk for Microsoft Windows on a clean server".
It has a valid reason, because when you install a Plesk panel, the components required to build the Windows Hosting environment is installed by Plesk itself. It's installation wizard provides you with the component/roles/software/server selection to install your choice of software in Windows system.
That means, it won't recognize none of your pre-installed components, and you won't be able to manage them from Plesk. Hence, it's not recommended to install Plesk in a production VPS as it may also corrupt the functionality of existing environment.
If control panel is your only concern, I would recommend you SolidCP. It's a free control panel built for Windows VPS. The best thing is, you can install it on your production setup without interrupting its functionality. It'll easily recognize the installed components/roles/servers allowing you to integrate them with SolidCP.
Installation part is straightforward - once installed you just have to integrate the existing server components in SolidCP and then you could easily manage them from SolidCP. It also allows you to import your existing databases, websites, domains, etc. from SolidCP to manage them.
I am trying to get a DotNetNuke site running locally.
At the moment the site is hosted on a server and is functional.
I downloaded the website to my local computer and tried to compile it in Visual Studio.
I am getting all sorts of build errors and I am having alot of trouble getting it to run.
The version of DotNetNuke is very old. i believe it is version 05.06.02.
Any help or advice would be much appreciated.
While you can access some of the DNN code via Visual Studio, first you need to get the site running without Visual Studio.
Here is a good set of instructions on copying and running a site on another computer.
http://www.ifinity.com.au/2012/09/05/Creating_a_test_copy_of_your_DotNetNuke_website
The main things to pay attention too are getting a connection to your database, and making the IIS site accessible locally.
We work for a small firm and we just started getting few SharePoint Projects.
Setup what we have done:
Purchased a new server and installed SharePoint 2010, SQL 2008R2, Visual Studio 2010 in the same server.
Created the application in the SharePoint Central Administration.
Developers directly login to server built the project using Visual Studio. (In server, only 2 ppl can login and work)
Issue:
1. We started getting 2 more projects, and the count of developers became more.
We need to know how to set up an environment where all the developers can work.
Also need to know if there is any way that they can work from local and then we can push the application to the server.
We do not have budget to get one more server and install TFS, so need to know if there is any other repository where we can make the above task possible.
Any help from all you people will me greatful.
Expecting a reply at the earliest.
Regards,
Alex
Depending on what specification laptops/PC's you have you may be able to create a virtual machine to do the development within. All the licenses here would be covered by MSDN subscription(if your devs have this) I think. VM's can get very big so what all the developers did in my last company was to have an external HD with our VM's on there, i think we were using e-sata connected external hd's
If you have TFS you should be able to connect the VM's up to this which essentially would allow you to use the build functionality to create your WSP packages ready for production(once testing has passed on your VM obviously), this package can then be dropped by TFS automatically to your production server ready for installation.
The great thing about this model is that you can have multiple VM's so if you break one you can just use a fresh one! All developers will be on a different VM but with some configuration would be working from the same source code.
Essentially this method has it's drawbacks and it's positives but i found this way was really benificial to me as i was learning how to do things and regularly needed a new VM :P
Something to note about what you have said, It is not recommended that you have VS on your production server.
Hope this helps
Truez
I'm working on asp.net project using VS2010.
I want to share my project code with one of my team member who is at some other geographical location but as we don't have a server we are not able to use TFS.
Can anyone tell me how can I share my code?
Or somehow can I use TFS on my local machine (or any other VS extension) and share it with him?
So that by using internet we can share our code with each other with help of any tool like TFS?
I would however recommend that you use TFS Preview to achieve this as it is free and provided all of the same goodies as having a local server without the need to run even a local server.
However if you must have local storage you can use TFS Express. It is free and will run just fine on your local computer. All you then need to do is expose your computer over HTTP and you are good to go.
Have you considered using distributed version control such as Mercurial? I do not know whether these systems can run serverless, nor do I have personal experience using them, but I've heard good things about the concept.
I have an Office solution for Word 2007 that I publish using ClickOnce. When I publish it to a local directory, I can install the .vsto file and everything works. When I publish it to our web server, though, I cannot install it. The error I get is:
Downloading file:///C:/DOCUME~1/Dave/LOCALS~1/Temp/Application Files/MyApp_1_0_0_0/MyApp.dll.manifest did not succeed.
I have been Googling for most of the day, and have already tried the following:
Added the correct MIME types to IIS 6 config (as described here and here on MSDN).
Created a test certificate, imported it into my trusted root authorities, and signed the app with it.
Published the solution to a network share and tried installing from there. It worked fine.
Tried accessing the MyApp.dll.manifest file directly from the web URL. The browser is able to find the file just fine.
What am I missing? Thanks.
Make sure that Windows Installer 3.1 is installed on the end-users PC. If it's not, you may want to add it as a prerequisite to your application.
Also, you may want to check and see if the application is installed from the Windows Add/Remove Programs screen. If it is in the list, you may need to uninstall the application, first. I know, you're probably thinking 'But the application hasn't been installed yet.'
Quite a few application that are published via ClickOnce. ClickOnce works great most of the time, but every now and then I see users who run into hiccups similar to yours when they try to initially install the application. The best solution is to usually uninstall all prerequisites, reboot, manually re-install the prerequisites (not from the ClickOnce setup.exe file) and then launch the application.
Some of those steps may not be necessary but it tends to fix the problem nearly every single time.