I have some question regarding VB 2019 RDLC report sharing to the client.
I am creating a setup .exe file for my application and install it locally, it works perfectly on my local PC.
Now I share the .exe to the local client PC, the client PC can access it with no issue
When I set the report reference, the client site is not able to access the report. What I have tried:
manually drag the .dll file to the .exe file location, but no work
manually add the .dll assembly file while creating the setup, but no work
remove the report reference, it works, but I want to use the report reference in order to generate barcode
Can I know any way to solve this problem or any way to know which file is needed to install in client side while I deploying the report with my application?
In my project i sent the barcode image from my code inside the list, table, etc. Along with all data
Related
i want to host a vb project from a sharepoint folder instead of having it locally installed.
I am still new at this, but I only need to host the files in the same folder on sharepoint right? And then whoever can just click the .exe file, correct?
Sorry if this is a dumb question!
Thanks in advance
As already mentioned in the comment SharePoint isn't meant to store or even display applications (.exe). What started as a security measure is now part of the philosophy of MS SharePoint. Here's a list of all filetypes SP13 will block by default.
Back to your question. There is a trick how you still can upload an .exe to SharePoint:
Store the application in a folder
Zip the folder
Upload the zipped folder to a document library
Display the library on the desired site
For the future..
As there is a "Silverlight Webpart" - develop silverlight application if you know from the beginning that you want to display them on SharePoint.
Another trick: Publish your application on a host server. Then use the "Site Viewer WebPart" and point it to your application
Last one, although I wouldn't suggest it.. You can develop a .wpf-application and simply upload it as the file-type isn't blocked. But to embed the resources is just a pain in the ass..
There are for sure many other ways to do this.. Those are just the most practical ones I know if you already developed the application. The best solution is of course to create your own WebPart..
I'm somewhat new to deploying ClickOnce manifests, first off. I know the basics of how to publish to an app server, which then lets every use the newest version (after setting to check for updates before running the application).
We have multiple VB.Net applications stored on our app server, that cover a lot of different areas of the company. However, all of them connect to our Oracle database in the same way. So, my thought was to create a DLL containing commonly used functions, such as decrypting and reading our connection string, among some very common SQL functions/statements that we use a lot. Then, instead of copying and pasting the same code into each .Net program, it would be stored in one place. Of course, the major benefit to this would be that if we change the method we use to connect to the database, or need functions modified/added, we don't need to open each program, paste it in, and .republish
So, I did a test where I took a program that I wrote, added the DLL to it and tested it out. It works great. Then I took the source code of the DLL, made a change to show a message box at the beginning of a function, rebuilt the DLL, and dropped it in place of the copy that was being referenced in the test program. When I run the program, it's still using the original DLL without the message box code.
My question is, how could I accomplish what I would like to do without having to republish each and every .Net program that uses this DLL whenever a change is made to it?
Option 1
Instead of publishing your dll library via click once, Put a web service wrapper around your dll class library. Each Click once application will have a reference to the web service which will run on a web server.
Your code in the dll will then be running on the web server. Any changes to the dll code will only need to be updated on the web server. You'll have to be careful to keep the interface changes to a minimum.
Option 2
push out the dll as an separate MSI install. Reference the dll in your click once apps code and make sure you don't deploy the dll with the click once install. Changes to the dll will be pushed out separately.
I have a program that uses access database to store the information. The problem I am encountering is when I shared from my desktop and I go to another desktop it doesnt want to add a new record or the query that is appending the information is not working. It only works in the desktop that I ran the msi. Can anybody help me what I am doing wrong. I am not using remote desktop nor team viewer. I am not using remote services like remote desktop or team viewer. First thing I ran the msi and install the program in my desktop. Secondly I got to my c drive and share that forlder where the program lives. Third I go to another computer click on network and I look for my computer and go to that folder and run that application. Next I tried to test my program by adding a new record but it gives me a message there is no query to update this record. I go back to my desktop and it works find.
It's because the program is referencing to the location of the database on THAT pc you're running it to...
C:\ on your pc is not same C:\ on the other pc.
I have a web application written in VB.NET. In my application I have a few RDLC reports that will be generated dynamically. Everything works fine during the development. But those reports are not working after I deployed my web application to IIS. Here are my problems.
(1) All the reports under my RDLC folder are not deployed, I think this is the reason why I got the error “error occurred during local report processing”
My question is why this folder was not published, and what should I set to publish this folder?
(2) If I manually copy those RDLC reports to the destination folder, I got another error “failure: unknown user name or bad password”
My authentication mode is set to Windows. Is there anything else I need to set in my web.config?
I am using IIS 5.1 and my web app has been upgraded from VS2005 to VS2010.
Your RDLC files are probably marked as "Embedded resource".
Right click on rdlc file and change it to "Content" and re-publish.
It will work this time.
I understand that you can't develop in Visual Studio 2010 for a remote Sharepoint 2010 server because you need a local copy running on your box. (I know there is a hack)
In my situation I have Sharepoint Foundation installed locally for development purposes but I'm not sure how to get the custom lists, etc from the remote server to my local box so I can develop against the same objects.
I've tried exporting the site on the remote box and then creating a new Visual Studio 2010 project from it. This resulted in exceptions when deploying to my local box - more problems which I'm sure given time I could work out...but more problems. (It was types not being installed properly on my local box that the custom object was using)
So I've been thinking there must be an easier way to pull down data structures.
I've spent a while looking for this and while there is quite a lot of information out there I'm finding it hard to find basic information like this.
Any help is greatly appreciated.
What objects do you need from the remote server?
If it is lists, you can export the lists from the remote server as templates then use the resulting stp files to create the lists locally. If it is dlls you can get them form GAC and add the required entries in SharePoint site web.config.
You can also try to export the entire site and create a site locally based on the site template.