1
0
mirror of https://github.com/chylex/TweetDuck.git synced 2025-05-05 20:34:07 +02:00
A Windows Client for TweetDeck. Not affiliated with Twitter. https://tweetduck.chylex.com
Go to file
2016-04-24 14:19:20 +02:00
Configuration Fix LockManager to check process name before reporting, and cleanup Close/Dispose code 2016-04-23 16:51:11 +02:00
Core Add address check to notification form before running notification.js 2016-04-24 14:15:04 +02:00
Libraries Add license output and add CefSharp license 2016-04-12 17:02:59 +02:00
Migration Change namespace to TweetDck 2016-04-15 13:23:40 +02:00
Properties Update version to 1.1.1 2016-04-17 17:42:14 +02:00
Resources Remove getFontSizeClass from code.js 2016-04-24 14:19:20 +02:00
_postbuild.bat Add a post-build batch file to delete unwanted files from the release folders 2016-04-12 18:07:37 +02:00
.gitignore Initial commit 2016-04-09 14:58:23 +02:00
LICENSE.md Rename LICENSE to LICENSE.md 2016-04-16 16:16:30 +02:00
Program.cs Update version to 1.1.1 2016-04-17 17:42:14 +02:00
README.md Add VC++ 2013 redist libraries 2016-04-16 14:10:40 +02:00
TweetDck.csproj Move update notification code to update.js and make the notification display without needing the app div 2016-04-23 17:54:15 +02:00
TweetDck.sln Rename the project and solution to TweetDck 2016-04-16 16:20:33 +02:00

Build Instructions

The program was build using Visual Studio 2013. After opening the solution, make sure you have CefSharp.WinForms and Microsoft.VC120.CRT.JetBrains included - if not, download them using NuGet. For CefSharp, you will need version 49 or newer currently available as a pre-release.

PM> Install-Package CefSharp.WinForms -Pre
PM> Install-Package Microsoft.VC120.CRT.JetBrains

TweetD*ck comes in two variants - TweetDick and TweetDuck. The solution includes both configurations under the names Release Dick and Release Duck, so make sure to select the correct one, or build both using Batch Build.

After building, run _postbuild.bat which deletes unnecessary files that CefSharp adds after post-build events >_>

Built files are then available in bin/x86 and/or bin/x64.