I specifically want to be able to use Ackmate bundle, peepcode (the new 'Go to file' seems good enough) and some other custom bundles with TM2.
I tried moving the existing bundles to a location
~/Library/Application Support/TextMate/Managed/Bundles/Managed
which seem to contain all the new installed bundles, and a few other hack. But no luck yet.
I did manage to get the older themes working with TM2 though, with an approach similar to the one above.
EDIT:
I found this article on the topic.But still not able to get some older bundles to work.
http://blog.macromates.com/2011/locating-bundles/
Just copy all your bundles from ~/Library/Application\ Support/TextMate/Bundles to ~/Library/Application\ Support/Avian/Bundles/
I did not find much success with the above. I guess its stil in 'Alpha'. Although you might try to drop some of the older bundles into
~/Library/Application Support/Avian/Pristine Copy/Bundles
to get it working with some hacks for now.I have managed to get Cucumber, Uber Glory and some of my custom bundles working.
Also you can follow the README of this Whitespace bundle to figure out which directory to place your new bundles in. This seems to be only bundle (not packaged) exculsively for TM2 so far.
The Textmate url that explains the difference between
Avian/Pristine Copy/Bundles/
and
Avian/Bundles/
is here:
http://blog.macromates.com/2011/locating-bundles/
It didn't recognize my old bundles at first, but the second restart of the app worked for me.
Since this is alpha software, I think that the mailing list is the best venue for your question. Either way, I haven't yet seen anything definitive on the backward compatibility of bundle support.
Related
I am using DNN 9. I recently upgraded DNN from version 9.1.1 to 9.3.2. When I Login, the left side of DNN disappears with only the logo od DNN. Other options like settings,edit etc are not seen. Any Idea as to what the issue might be?
If you search the forums at dnnsoftware.org, you'll probably find the solution. I'm afraid that I don't recall what it is.
I think, though, that upgrading to 9.4.4 will fix it, too. You'll want to do that in a test environment to make sure that your upgrade will work. There may be some third party modules that need to be upgraded before you upgrade to 9.4.4, so check with module vendors.
As an addition to Joe's answer: There were Problems with the Newtonsoft JSON versions. Maybe this thread is helpful: https://www.dnnsoftware.com/forums/threadid/543186/scope/posts/persona-bar-not-displaying-completely
"...so check with module vendors": There are known issues with DNNSharp modules. See https://dnncommunity.org/forums/aft/748 - but better check with all vendors of third party extensions, if you use any.
Read a few things, tried this and it worked. Delete all from the Bin directory, grab and copy all from another bin directory from a currently working site with the exact version. You may need to install a demo/test site and spin it up to get a good working copy, but this worked for me.
Restoring the bin folder was the solution for me
I am sorry for this stupid question, but I really need to install version 3.9 of the Wix Toolset. I can only find version 3.10 and 3.11. There is a link on the website to download older archives (also for 3.9rc2), but in this 1.2Gb file I cannot find an installer.
Please do not tell me to install the latest version, I have my own reasons for 3.9 that goes beyond the scope of this question. Any help is truely appreciated.
I should leave this for the WiX guys to answer, but maybe you are very busy and just need to test something?
Building it yourself from the sources isn't an option is it? https://github.com/wixtoolset/wix3/releases (towards the bottom, click the blue image - it says "Show 5 other tags" here). Sounds painful to work that out...
The 3.9 binaries seem to be here (looks like R1): https://github.com/continuoustests/ContinuousTests/tree/master/Installer/ContinuousTests.WixInstaller/wix39-binaries, but not as an installer file. Maybe you just need to test something quickly? If so, obviously please accept your own risk here, I am not sure what these files really are.
I hope I haven't linked to something that is problematic, just delete the whole answer if this should be the case (i.e the binaries pointed to should not ever be used - for some reason, etc...).
I recently had a need to get the old wix38.exe installer for legacy project maintenance, and it was a pain. Tom Blodget's comment above was the key on how to find the required file from the CodePlex archive.
Because there are likely to be other people in the future who require access to these things, I've created a github repository https://github.com/CasaDeRobison/wixtoolset-codeplex that includes the state of the git repository from the CodePlex archive and also makes available the various files from those releases at https://github.com/CasaDeRobison/wixtoolset-codeplex/tree/master/archived-stable-versions
Hopefully others will find this useful as well so that we don't all have to collectively puzzle this out if we have a need for this older software.
I really like the idea of this BundleTransformer plugin from NuGet, and I see that they have LESS support. But ...
After weeks of trying, I cannot find any decent example of how to use it. The documentation is unclear, to say the very least. This is the closest I could find, which does not compile or work.
who-could-ask-for-more-with-less-css
Well, the simple answer is that I could ask for more.
Can someone please assist me with the simple task of creating a bundle that has .less files in it, that will run? I am completely lost.
I would suggest reading the wiki page for bundle transformer and also, as the wiki page suggests, make sure you are familiar with ASP.NET bundling and minification.
If you follow the examples of usage you should be up and running.
I know this is an older post but figured I'd chime in. The Bundle Transformer Codeplex discussion board (Feb 2015) mentions that BundleTransformer is no longer considered a modern client-side build tool and they are recommending you go with Gulp or Grunt - which both have support starting in Visual Studio 2013.3 via VSIX extensions and more baked in to VS2014. FYI -This Scott Hanselman post explains how to get up and going with Grunt and Gulp in Visual Studio. I think if you're using BundleTransformer for simple Less compilation it works fine, but doesn't allow you to do things like generate CSS Sourcemaps which make your browser's dev tools aware of the Less source files, which in my humble opinion is critical for using a CSS preprocessor - the ability to see the LESS line numbers of your source files in the styles pane.
I have just jumped on the Sublime text wagon and really want to optimise my workflow using LESS. I have looked for a plugin that performs the compiling clientside, in fact I could just add the less.js file to all projects, but I can't find anything to explain how to get it to work.
Also I was thinking that it would be best to install something on the Apache server that comes with MAMP to do it server-side and then I wouldn't have to worry about adding certain files and copy the preprocessed client-side code for the production website.
I use CodeKit (Mac Only), which does what you want SO WELL, plus so much more. I really can't say enough good things about it. I'd recommend checking out the site and the videos to see what it offers.
There is also this ST2 plugin:
https://github.com/BBB/sublime-text-2-plugins
I haven't used it personally because of how well CodeKit works. But it is another option.
Just to clarify, these aren't options that install and run on MAMP, but I think once you check them out you'll see they still provide a solution that doesn't require you to add extra files to your projects.
I found that Wix v3 uses a tool (heat.exe) to "harvest" information into WiX fragments. Either I am looking in the wrong location, or this is thinly documented.
What is the best way to auto-generate a WiX fragment (likely using heat.exe) for a complex folder structure that contains media files:
Of varying types (ico/png/xaml/etc)
That may change regularly (names/locations/adds/removes)
That are classified as "Content" and included in a .csproj
such that they can be built into an installer via WiX and would withstand upgrades and patches with decorum?
Background Information
I found heat.exe, which seems to solve the autogenerate WiX fragment requirement
In getting the "dir" harvester working, I noticed the "project" harvester (commandline help)
Media is already in C# project file, and so noted that "-pog:Content" might do very well
Cursory search found out of date documentation that didn't mention "project" harvester
Realized entire project installer could probably done with "project" harvester, but was unsure how well this was supported, and what the pitfalls were.
Saw the generation of "PUT-GUID-HERE" and realized that autogeneration of guids would likely have upgrade/patch implications.
Realized that there must be people who use these tools for similar purposes and could probably point me in the right direction.
It was (fairly) pointed out that v3 is not yet "done" (thus the scarceness of documentation and tutorials). The sense that I get now is that it is non-trivial to automate this in my build scripts, and the tools are growing right now to ease this.
In my experience John Robbins' Paraffin solves alot of the issues with tallow.exe (heat.exe in v3). I'm not sure if Paraffin plays nicely with v3, but it might be worth checking out.
FYI, I've used Paraffin in a build process and it allowed me to remove the previous 2-3 step cleanup process that involved a powershell script.
For the upgrade implications of auto-generated setups, read this. The take-home message:
Windows Installer doesn’t let you
remove components in a minor upgrade
It is hard to guarantee that components continue to exist if you generate your setup automatically. Therefore you have to chose between auto-generation of components and the ability to do minor upgrades.
If you have some auto-generated components, then just stick to major upgrades. You can use this sample by Rob as an example.
Thanks for the background, I wasn't aware that they were working on a new version of Wix. According to the project page, it isn't RTM yet, so that may explain the problems you're having. I hope to hear from the WIX developers in one of the replies.
I can't help you use the under-development heat.exe features. However, I have been in your situation and my solution was to create a tool that took directory and file information as input and generated valid wix project files as output. A .vsproj file is just an XML file, and you can use XSL, C#'s LINQ, PowerShell, or a number of other tools to do the work. I personally have used (pre-LINQ) C#/XMLDOM to parse VS project files for this purpose.
Good Luck,
Dave
For documentation, check out the help file that is installed with WiX - WiX.chm provides the most up to date information (along with the command line -help option).