Sorry was busy I'll try it :O
@SuperJMN i think you can setup AppVeyor to automatically publish nuget packages
@SuperJMN you could publish to your own private feed which is simply a folder on your local PC. that way you can keep using NuGet packages and don't need to introduce unnecessary dependencies to Git submodules, which are IMO horrible :S
there are quite some build scripts which allow you to automate your NuGet package process
see http://docs.nuget.org/Create/Hosting-Your-Own-NuGet-Feeds for the feed thing. for the packaging process there are a lot of ways. starting from a simple batch file to VS extensions that do that to full-fledged CI servers (which are probably not an option here)
@SuperJMN i think you can setup AppVeyor to automatically publish nuget packages
I've read AppVeyor somewhere, but I have never used it! I will take a look
@SuperJMN you could publish to your own private feed which is simply a folder on your local PC. that way you can keep using NuGet packages and don't need to introduce unnecessary dependencies to Git submodules, which are IMO horrible :S
Interesting... you say that modules are horrible. But could you tell me why?
see http://docs.nuget.org/Create/Hosting-Your-Own-NuGet-Feeds for the feed thing. for the packaging process there are a lot of ways. starting from a simple batch file to VS extensions that do that to full-fledged CI servers (which are probably not an option here)
Extensions for VS 2015? I used some extensions that generate NuGet Packages automatically and uploaded them. But nothing for VS 2015 for now :S
@SuperJMN it creates a hard dependency on the VCS and is IMO more cumbersome to handle, especially if you're not familiar with git or simply go to your repo page and hit "Download as ZIP". last time I did that with a repository that relied on submodules the modules were not included in the zip file
OK, I'll annotate that :)
you can still do stuff like that: https://github.com/MahApps/MahApps.Metro/blob/master/Build/build.ps1
but, is there currently a dumb-proof method to create/upload NuGet packages without much hassle?
if you're lucky I'll fine that lib again I stumbled upon a few days. it allowed you to create NuGet packages right from your C# code, which I find very neat
Uhmmm, PowerShell?
you're not a fan of PowerShell, are you? :P
haha, I've worked with it
and I know the basics
but I don't really like it :)
:D
haha
well, do you need to automate the process during (local) development or do you need something for the future to also upload it to the NuGet library itself?
yes, that's it
I had a very nice extension that did just that
It detected dependencies and everything
NuGet Packager, if I remember well
isn't that what NuGet also does if you use the .csproj file?
I don't know
I think you have to specify everything in the nuspec file
lib, dependencies, profiles...
See "From a project"
as alternative you could also modify the VS extension to allow it to work with VS2015 :P
O_O
haha
you mean, modifying the vsix?
BTW, thanks for the shower of information!
you're welcome. glad I can help :p I'm more of a NuGet package user and not much of an author :D
but you seem to have dealed a lot with NuGet
otherwise, you wouldn't know so much about its automation
:)
yeah, or... https://bitbucket.org/azzlack/nugetpackager/issue/2/support-for-visual-studio-2015 :P
I'll try to get it!
Right now I'm trying to fix my VS 2015 RC
suddenly, the Git integration died!
the Team Explorer shows an exception in the tabs
heh :D is it possible that you've got the VS GitHub extension installed?
hi guys
i think it's easy to set up a nuget package feed that just points to a directory on your computer
so that way you don't have to worry about uploading to nuget.org
i think it's as simple as adding a build step to create the .nupkg then pointing nuget in VS to the directory that the .nupkg is in
@grokys I'm not sure how to do that. I would to have it so anyone can just clone and build.
sometimes, when integrating with Perspex, I discover something that I have to fix in OmniXAML
i think win2d used to do this when it was in early development
under "getting those bits" it tells you how to use a local nuget source for win2d
you can then add a nuget reference in Perspex to omnixaml
without uploading it every time to nuget.org
then you can just upload versions when you've finished a feature to nuget.org for everyone else to use
the nuget reference will use the local source if available, and if not it will go to nuget.org
(assuming the local source is higher on the list)
nice approach!
I think I will do that
how do you generate packages?
for win2d you had to run the build.cmd
nuget.exe?
but you could add that as a post-build step
i think build.cmd just calls nuget.exe
you could also add it to a separate solution configuration, so it would only be run when you're developing
OK! I think I will try some different methods to see how it fits :D
thanks for the options and the info!
By the way, @grokys I think there is some problem with the menus :(
(and the TreeView)
they don't load OK
yeah, menu in particular is still a work in progress - treeview i've not looked at for a while
oh... do you mean they don't load from XAML?
sorry, I was out!
yes, the TreeView just don't load
I seems there is something bad there
I haven't taken a look in the insights
It shows some kind of exception that enforces TreeViewItems to be children of TreeViews only
it happens with this snippet
<TreeView>
<TreeViewItem Header="Root 1">
<TreeViewItem Header="Child 1" IsExpanded="True" />
<TreeViewItem Header="Child 2" IsExpanded="True">
<TreeViewItem Header="Grandchild 1" />
<TreeViewItem Header="Grandmaster Flash" />
</TreeViewItem>
<TreeViewItem Header="Child 3" />
</TreeViewItem>
<TreeViewItem Header="Root 2" />
</TreeView>
but it fails also with
<TreeView>
<TreeViewItem />
</TreeView>
I cannot debut it right not because I had a big mess with my VS installation that didn't allow me to do anything with Git
and I reinstalled the whole OS!
madness, yes! but I was feed up trying to solve it :S
(debug, I mean)
OK! I'm debugging
this XAML
<Window Title="Perspex Test Application" Height="350" Width="525" xmlns="perspex">
<TreeView>
<TreeViewItem Header="Root 1"/>
</TreeView>
</Window>
Crashes at ItemContainerGenerator.cs, line 134.
Message: The key has already been added.
paramenter item => {Perspex.Controls.TreeViewItem}
surprise... the parameter item and container are... the same object!
it looks like the item is trying to be added as child of itself!
Uhmm, maybe it's because TreeView.Items is a collection of TreeViewItems!?
after having debugged the code a bit, I can see different paths in the code when loading from XAML
the Visual Tree is the same
a Window with a TreeView with a TreeViewItem
but ItemsChanged is called different parameters
I don't know why, but it only happens with the TreeView
I'm going crazy :anguished:
Maybe tomorrow I can prepare a branch for you, should you want to take a look
I give up for now
:S
today it has been a hard day
and I'm not talking about programming
I don't have much energy. See you tomorrow. I'm off.
have a good night!