I'm using a project the references EntityFramework.dll and EntityFramework.SqlServer.dll; I've always wondered why, whenever I Build (in Release mode) it always produces 2 xml files in the \bin\release directory...
I have never deployed these xml files, and looks like they are useless for deployment purposes. So what do these two files do?
Related
I have three files ImgProc.h, ImgProc.lib, and ImgProc.dll created by Matlab. I imported them to my VSC++ 2012 MFC project, but when I ran it, the error occurred. I did add the ImgProc.lib into the linker-> input->additional dependencies, Copied 3 files into project directory.
I could not add references. Because when I tried, it was empty like:
that
I really appreciate if someone could help me.
ImgProc.dll must be available at runtime in your application's directory. You need to manually copy this file to your output directories for both Debug and Release builds. Alternatively you can create a post-build step that does the copying. Having ImgProc.dll in your project directory is not enough - your project directory is not part of the Dynamic-Link Library Search Order.
I use Capifony to deploy my Symfony2 project to the production server. As a result of the deploy:setup task, folder called /shared/logs were created. However the symfony2 actually refers to /shared/app/logs to store the log files while the shared/logs remains empty.
Anyone know what's happening?
The shared/logs folder is no more created since capifony version 2.1.7.
I've just checked the latest capistrano deploy recipe in trunk and it seems like this's a default behaviour of Capistrano instead of Capifony. It create folders using only the last part of the path of the shared_children array instead of including the full path. Later on in the task deploy:shared_children of Capfifony it create the sub folders with full path.
I have several source files (all in one Group) that seem to compile with the project, but I cannot step into them or set any breakpoints within.
These files are newer versions of the same files I had in my project. (I updated the code I am using from a 3rd party). After the update, these newer files seem to compile with the project, but somehow they don't seem to be the ones the linker is putting in my final object (its like its using the older files).
So I can do this:
1. forcibly create a syntax error in one of these file and the compiler complains
I cannot do this:
1. hit a breakpoint in any of these files
2. step into any code in these files from a breakpoint outside
3. add a NSLog statement and see the output
Its like the project file (or something else) has its hand on the old compiled files (hence the project compiles fine and runs) and won't replace with these files.
help!
Sometimes it happens that the new version gets put in some unexpected place and that you indeed have two versions of the file in your project without noticing.
Do a project wide search of some unique content in the old and new files. You should get both files displayed and you can delete the old one.
Are you running in release mode? Breakpoints and NSLog statements don't execute when you build and run in release mode.
Set your Active Build Configuration to Debug.
What should I check in/not check in? Since many of the files are sometimes auto-generated I'm not entirely sure how to handle this using version control...does it have something to do with tags?
For instance in ANT, I know not to check-in my target/bin directories...but Grails adds another level of confusion to this...since some of code is generated and some of it is not.
(It may become clearer as I go...but it seems to be that there needs to be some way of being able to tell what was just generated and what was modified by a developer so that it needs to be placed in version control)
Here's the .hgignore directory I've got on my most recent grails project (with a couple of project specific things taken out):
syntax: glob
out
target
logs
*.iml
.idea
*.iws
*.war
workspace.xml
lib/build
lib/compile
lib/runtime
lib/test
~$*
stacktrace.log
*.tmproj
*.launch
reports/
*.orig
*.zip
.DS_Store
*/.DS_Store
web-app/WEB-INF/classes
cobertura.ser
The generated code in Grails should be placed under version control. It's not secondary executable code that is generated by the build process like class files, but instead is code that is part of your source. The generated code is intended to be just a starting point for your application and will most likely be modified at some point anyway.
Also check this:
http://www.grails.org/Checking+Projects+into+SVN
and this:
https://stackoverflow.com/questions/4201578
I'm trying to get my ad hoc build distributed but have started experiencing problems. It used to work up until around a week ago, but now ITunes gives an 0x8008017 error when I try to Sync.
I've narrowed it down by using the iPhone Configuration Utility and then discovering the error seems to be coming from a failed code sign. I've ran codesign -vvvv myApp.app and the outup lists a load of missing resources from my Help documents (from my Apps Resource folder). each missing resource begins ._ so for my index page:
01 - Index.html
the codesign is also expecting: ._01 - Index.html
It also has the existing file listed (as it should) but fails because all ._files are not included in the app.
I've looked through my projects directory and can't find any files beginning with ._ so am not sure where the codesigner is getting these filenames from, but they are included every build, after a clean or an Xcode restart.
All the resources that are causing problems are all recently updated files that I copied over the old resources at the beginning of the week; might this be something to do with it?
Any help appreciated
Make sure you do one of these:
copy those files with an Xcode Copy Files phase, which should Do The Right Thing by default, or
exclude resource forks and ._* files if you copy through a script, or
make sure you build on HFS volumes (where ._* files are not generated for resource forks).
Sounds like your partition type is generating resource-fork files which are also being signed as separate files in the bundle, rather than as part of the original files (which is bad); and then, they're also not getting copied (if you use Finder zipping, they'll be removed and set aside in a different portion of the Zip file, IIRC), again bad. Avoid having them in the bundle, so they don't get signed and you don't have to wade through this mess :)