In the Intershop 7.9 project I'm currently working on the development server doesn't seem to monitor the ISML files for changes. This means a cartridge rebuild is necessary before seeing any ISML changes. In previous projects I've worked on (ISH 7.5, 7.6, 7.7) this was never necessary, just saving the ISML file was enough.
It feels like I'm missing something really simple, but I can't seem to figure it out. So far I've tried the following without success:
Made sure page caching is disabled.
Redeploying the server by running the command: gradlew deployServer
Enable hot code reloading by running the command: gradlew enableHotCodeReloading.
Checked the gradle.properties file located in GRADLE_USER_HOME, all cartridges I expected to see are listed as sourceCartridges.
Checked the environment.properties file, as far as I can see this file contains no properties that would do anything for live code reloading.
Reinstalled Intershop Studio.
Any suggestions on how to fix this would be greatly appreciated.
As far as I remember there were some relevant properties in appserver.properties. I've googled these by chance:
# perform a lookup and compile the ISML template, when it exists
# and is newer than the cached version
intershop.template.CheckSource=false
# the time interval in seconds, after which a full lookup should be performed,
# if CheckSource is "true". 0 means every time
intershop.template.CheckSourceInterval=0
# should the last cached template location been checked for a newer version of the
# template, if CheckSource is "true"?
intershop.template.CheckSourceModified=false
Now try with these values:
intershop.template.CheckSource=true
intershop.template.CheckSourceInterval=0
intershop.template.CheckSourceModified=true
I think that if you do not want to loose your changes on server redeploy then you may put the snippet above into a file named development.properties located in the same directory as appreserver.properties.
Make sure the necessary checksource properties are set in appserver.properties. In your case the settings for templates need to be set to true.
Related
I am using aspnet_complier command for building website, first time it is compiling complete website i.e all pages, but after modification on the site, it is again compiling all the pages. It should compile only that pages that have been changed or modified.
And other things are
1) How can i speed up the aspnet_compiler ?
2) how can i exclude warning from the output ?
Please suggest on the same.
According to the documentation, "You can also recompile an application in place after adding new source files to it. The tool compiles only the new or changed files unless you include the -c option".
Unfortunately, there doesn't appear to be an option to hide warnings.
Speed up the process by making sure the machine where you run it is appropriately powered. eg. an SSD disk should probably help.
I hate to ask the same question others have asked in Stackoverflow, but I still can't figure out why Installaware 7.0 R2 has this problem.
I need to build a installable CD for the previous version of my software. So, I am using what came with RAD Studio XE to do this. After creating a new Win32 setup for installation and customizing it, I built and test ran the project. In the middle of the installation, it raised an error, "Error Folder Path 'C:' contains an invalid character." So, I went back and created another win32 project and without doing any changes to anything I compiled, built and test ran the project. It worked without any error. After spending hours changing one thing at a time and testing it over and over again until I hit the error message again, I finally found the offending property in the Installaware. The error is raised thereafter once you change the Target folder textbox default value which is $PROGRAMFILE$\$TITLE$\ or Shortcut folder textbox default value which is $TITLE$. They only way to get passed this error is by not changing those default folder paths and allowing the user to change the folder path during installation.
It sort of annoying especially when you spend thousands of dollar purchasing these software from Embarcadero and Codegear. Is there a fix for this? Does anybody know?
These variables are resolved automatically to full folder paths. If you delete them or set an incorrect value, your package will not be able to resolve the installation path (hence the error). So the path edit controls should have valid default values.
If you don't want to allow the user to change your installation path, you can try deleting the dialog which offers this option. I'm not sure if that version of InstallAware supports it though.
If you don't like InstallAware, there are some good free or commercial alternatives which may help you.
I am building my first iPhone app. I am using XCode 3.2.6. Everything was ticking along fine when all of a sudden, I get this strange build error. The message is shown below:
GenerateDSYMFile build/Debug-iphonesimulator/buddy.app.dSYM build/Debug-iphonesimulator/buddy.app/buddy
!error: unable to open executable"
From what I have managed to figure out, there is a file called buddy.app.dSYM that resides in my /build directory. If I clean my project, then build, it appears and everything is fine. However, if I build a second time, I get the error. If I build a third time, the error is gone, 4th time, I get the error again. And so on.
The error is consistent with the presence (or lack of) my buddy.app.dSYM in my build directory. ie, it is created, deleted, created, etc ...
So it seems like something is deleting the buddy.app.dSYM file every other build.
I recently started working with SQLite in my project. Other than that I can think of no major changes I have made to my project.
Any ideas?
Update
I can't put this as an answer because I am new to the system and not allowed. But .....
A: I think I figured it out. I struggle all day and then 5 mins after I post I get the answer. Figures. Anyway, it was to do with the SQLite database I had included in my project under the Resources tab. I had included it, but then deleted the .sql file. I recreated the file, but with a different name.
So I removed the file from my project and reimported the new .sql file. And no problems since.
I have no idea why this created such a funny error. If anyone knows, please post.
I have a problem debugging a web forms application that is configured to use IIS for debugging, under Windows 7 and Visual Studio 2010. An example has just occurred, where I make a change to the code behind for a web form, save, and apparently rebuild before starting the app using F5.
The app starts, and I get an error message trying to do something in the app. I tell the debugger to break when an exception is thrown and try my task again, only to be told
The source file is different from when the module was built.
where the module is C:\Windows\Microsoft.NET\Framework64\v2.0.50727\Temporary ASP.NET Files\root\9d7b45ca\11a98b19\assembly\dl3\5e6cf0b2\636409d4_dfeecb01\PerfixEMS_Admin.DLL
The physical folder for my test web site is set to the web application project's source folder, so I have always assumed that IIS will look in the bin folder for required assemblies, and these will be rebuilt as expected. Why is this not happening?
Cleaning the solution usually works for me.
Update
Given the high number (320) of projects I understand why Clean and Build won't work for you. You should however try it at least once to see if fixes things.
If it does fix your problem but doesn't last you'll need to do one of two things.
Clean just the one file
Delete the offending temp file. You probably won't be able to do this because with VS running since it may have a lock on the DLL. You may also have to stop IIS. You can use Process Explorer to look for the processes that have a lock.
Use a custom solution
Its unlikely that you're going to be modifing all 320 projects at the same time. Create a custom solution for just the projects you're working on. You'll still be able to step through any project you have the DLL and PDB for if you need to.
Which to do
Using a custom solution has its problems since you can no longer use project reference for projects not in your solution. This impacts your team's source control. You'll also have to make sure the DLL's and PDB's from outside your solution are in a stable location and you'll need a way to detect when thoes other projects have changes that you care about.
These problems can be overcome with a careful check-in process for Project changes and scripts that copy files and working with team members to figure out how to communicate changes.
On the other hand closing VS for every change or running Clean and build isn't really tennable either.
it may be a workaround, but I just need to see if it will work or not, then we may investigate more in the original case. but for now, try this:
1- publish this website to a different folder
2- open the newly published version from your preferred browser (ex: http://localhost/APP_NAME).
3- from VS, open "Debug" menu, choose "Attach to process..."
4- select the IIS worker process "w3wp.exe" and click "Attach".
(if you can't find it, make sure that the checkbox "show processes in all sessions" is checked)
5- start debugging your source code normally and let me know what happened, thanks.
I am running mxmlc in the command-line with -incremental=true. Flex is building the cache file using a checksum the first time. Subsequent compilations fail with this message:
Failed to match the compile target with path_to_cache/projectname_329043.cache. The cache file will not be reused.
path_to_cache exists
the cache file exists in path_to_cache
the compiler is not trying to create a new cache file, so I assume it is generating the same checksum
My environment:
Flex 3.0
Mac - OSX 10.4.x
I just ran across this issue myself and after not finding the answer anywhere on the web, I bashed my head against mxmlc in practically trail-and-error until finding the answer. In my case, I was regenerating the flex config xml file each time I compiled from within ant. It turns out that this is the error you get in the case where it thinks the config has changed. You can test this by simply touching your config file and running against unmodified sources. So, if the timestamp is changing on your flex config.xml between compiles, that is likely the culprit.
It could be a permissions issue. Have you tried running with sudo? I wouldn't recommend doing that permanently, but if using sudo makes the error message go away, then you know it's a permissions issue; and you can move on to the proper way to resolve it.
You could also try going into Disk Utility and doing a check/repair of disk permissions. OSX has been notorious for needing this done occasionally.