For dynamic linking, the documentation Connect_to_SQLite_database_(FireDAC) says that one should edit the firedac.inc file located at C:\Program Files (x86)\Embarcadero\Studio\19.0\source\data\firedac.
I can only find firedac.inc in C:\Users\Public\Documents\Embarcadero\Studio\19.0\Samples\Object Pascal\Database\FireDAC\Samples.
If I copy it to C:\Program Files (x86)\Embarcadero\Studio\19.0\source\data\firedac, and enable dynamic linking (i.e. remove dot as indicated $UNDEF FireDAC_SQLITE_STATIC) that does not seem to result in dynamic linking (I have a custom sqlite3.dll in same folder as exe).
How do I achieve dynamic linking with sqlite and firedac?
I am using Tokyo, although the same incorrect documentation exists for Rio.
I contacted Embarcadero Support and they confirmed this is a problem with the Professional edition, where certain source code files are missing.
The representative filed this issue with reference RS-95075. If you need the source code files you could contact Embarcadero Support.
somewhere along the line I was playing around and renamed a sqlite3.dll to sqlite3.copydll. Now my UWP project is referencing that dll. I have since changed it back to Sqlite3.dll what it should be but I keep getting the below when I build my project
Could not copy the file "C:\Users[username].nuget\packages\SQLite\3.13.0\runtimes\win10-x86\nativeassets\uap10.0\sqlite3.copydll" because it was not found.
I cant find where in my project it is still referencing this dll name.
Can anybody help
Open your .csproj as text and search for it there. Or remove reference to SQLite in VS and add it back.
In a project that I am working now, a new WIX setup project was added by a developer. When I'm trying to get the latest from the TFS that we are using for the code base, the newly added project is shown as incompatible and while building the solution following error is thrown:
Has anyone experienced this before?
In a typical team build, the TfGetSources activity will do a Get to retrieve the source files from TFS source code control. However the Get will set the Read Only attribute on all files retrieved, and any attempt to over-write any source code controlled file, during the build, will result in an Access Denied error.
Your new project is using the WIX toolset Heat.exe utility to generate the file C:\70_Suite\Accounting\IBS.Accounting.Setup\App.wxs. This file is under source code control which means it will be read only. The Heat.exe utility is throwing the Access Denied error because it can't over-write this file.
One solution is to remove C:\70_Suite\Accounting\IBS.Accounting.Setup\App.wxs from team foundation source code control. It is generated by heat.exe anyway, so doesn't need to be fetched by the TfGetSources activity.
If you need to keep C:\70_Suite\Accounting\IBS.Accounting.Setup\App.wxs under source code control, then a work-around would be to remove the read-only attribute from this file. This could be done in the Pre-Build Event Command Line in the new WIX project.
I'm doing the following steps:
Create an empty Notes Database (Lotus Notes 9.0.1 on Domino 9 Server)
Creating Xpage with only one Label
Inserting external Jar File (Code - Jars)
I tested this setting with different jar Files. In most cases there are no problems but I found 2 jar Files which produce an error 500 in XPage without being referenced
starface-rpc-1.6.442.jar
log4j-1.2.17.jar
Does someone has an idea what can be the problem?
Those two .jar files depend probably from other .jar files.
Look at the project pages like this for log4j to find out which .jar files you need to add to your application too.
Update:
Those .jar files stay in conflict with existing Java APIs used by Domino Server. That's why you get the error even without using them in an XPage as they get used by Domino Server executing an XPage.
Look here for explanation the log4j issue
I've run into this issue when trying to publish my application today that I have published many times before. I'm trying to publish to a directory.
The issue I have is, if I go to my app directory C:\www\clients\clientsite\app\clientproject\Properties\PublishProfiles where the error below says it can't find the file I can clearly see the git.pubxml file.
Copying file Properties\PublishProfiles\git.pubxml to obj\Release\Package\PackageTmp\Properties\PublishProfiles\git.pubxml failed. Could not find file 'Properties\PublishProfiles\git.pubxml'.
I've checked directory security settings and those are proper. I tried deleting my bin and obj but nothing is making a difference.
Often times the solution here is to edit the project file itself in notepad.
The trick to finding the afflicted path is to inspect the OUTPUT window, not the ERROR LIST window.
Once you find the afflicted file path, search for it in the project file and remove the reference.
In most cases the troublesome lines in the project file look like :
<Content include="{your path}" />
Continue to remove the includes until publishing works.
IMPORTANT: if you keep Visual Studio open while you're doing this, you must accept the "reload all" prompt.
I just ran into this after removing all unversioned files from my filesystem (which caused some .pubxml.user files to be lost.
If you right click the project node and click "publish", then select the publish profile that is causing problems, then simply close the publish dialog, Visual Studio will ask if you want to save changes... when you click yes, it regenerate the .pubxml.user file and everything works again.
Have you ensured that the file actually exists in the project? I have had problems working in a team where some file I wrote ended up not appearing in VS as a project file, so when we published, it didn't exist in the publish. If you can't find it inside VS, ensure that you are not debugging, and drop the file into the project file structure, then publish as normal.
VS was saying it couldn't find that file because the git.pubxml file in that directory was of type USER File and it needed to be PUBXML. When I added the correct file type from another version of that same project, I was able to publish the project again. I believe the PUBXML file was removed by mistake in source control.
It usually happens to binary files after updating it. Some packages remove it's own .xml and .pubxml files, while visual studio still believes that it is a part of the project.
What you need to do it to check for a Yellow Triangle besides the file name in the project directory tree, and remove that files, they're useless since your project compiles without errors.
try changing the publishing settings. if you check "Precompile during publishing" this will recreate your .pubxml.user file
I looked in Solution Explorer under the PublishProfiles section and found that the file was excluded and had a "!" by it showing a warning that the file wasn't found. I deleted it, then went into my Publish settings to edit a profile. I changed something (for me to compile files during publish.) Then I tried republishing the solution, and it worked!