These are chat archives for AvaloniaUI/Avalonia

19th
Jun 2015
can anybody try it?
José Manuel Nieto
@SuperJMN
Jun 19 2015 09:38 UTC
@cH40z-Lord Sorry!! I didn't see you trying to help me with the Git integration problem! No, I didn't have the extension installed. Everything by default. The funny thing is that it broke when I used modules in my Git repository. I'm not using them anymore, so I think it won't break again! Thanks a lot for your interest :)
Steven Kirk
@grokys
Jun 19 2015 09:44 UTC
@SuperJMN : yes those instructions seem to work!
only thing is i had to remove the call in the ctor to InitializeComponent for some reason
and update the .net framework version to 4.5.2
José Manuel Nieto
@SuperJMN
Jun 19 2015 09:45 UTC
oh my...
OK, did you put the Build action in MainWindow.xaml to None?
BTW, thanks for trying!
Steven Kirk
@grokys
Jun 19 2015 09:46 UTC
yeah
José Manuel Nieto
@SuperJMN
Jun 19 2015 09:46 UTC
I'm going to try again!
maybe it's better to just remove the code-behind file
Steven Kirk
@grokys
Jun 19 2015 09:48 UTC
ok, yeah, it's when you set build action to "None" that InitializeComponent disappears
José Manuel Nieto
@SuperJMN
Jun 19 2015 10:01 UTC
I fixed the guide! :D
"1.Create a new project of type "WPF Application" and be sure that you select at least .NET Framework 4.5.2 "
"4.Delete MainWindow.xaml.cs (the code-behind file). It won't compile if you don't delete it."
Steven Kirk
@grokys
Jun 19 2015 10:02 UTC
it does compile for me even if i don't delete it
just have to remove the call to InitializeComponent
José Manuel Nieto
@SuperJMN
Jun 19 2015 10:05 UTC
Since it's not used, I just ask people to remove it
it's my way of saying "you don't need that shit!"
But of course, I will need the code behind file for UserControls... oh mamma!
and other nasty stuff
Johan Larsson
@JohanLarsson
Jun 19 2015 10:37 UTC
Is removing code behind an important goal?
José Manuel Nieto
@SuperJMN
Jun 19 2015 10:39 UTC
in case you are using MVVM, yes
otherwise, code-behind is a must
for any view that is using MVVM, you shouldn't have the need to use the code-behind.
Johan Larsson
@JohanLarsson
Jun 19 2015 10:40 UTC
View specific stuff makes sense in code behind
José Manuel Nieto
@SuperJMN
Jun 19 2015 10:40 UTC
yes, sometimes :)
but I try to avoid view-specific stuff
Johan Larsson
@JohanLarsson
Jun 19 2015 10:40 UTC
I've seen all sorts of confusion around mvvm, listboxes shwoing up in the vm etc :)
José Manuel Nieto
@SuperJMN
Jun 19 2015 10:40 UTC
should be an exception, though
ListBoxes in the VM!?
DIE HARD!
Johan Larsson
@JohanLarsson
Jun 19 2015 10:41 UTC
My view is pragmatic but it is very rarely code behind is needed
José Manuel Nieto
@SuperJMN
Jun 19 2015 10:41 UTC
flamethrower for that
Johan Larsson
@JohanLarsson
Jun 19 2015 10:41 UTC
yea
José Manuel Nieto
@SuperJMN
Jun 19 2015 10:41 UTC
haha
anyways, code-behind is needed.
some custom controls NEED them
to define DPs, for instance
Johan Larsson
@JohanLarsson
Jun 19 2015 10:42 UTC
yep
José Manuel Nieto
@SuperJMN
Jun 19 2015 10:42 UTC
everything that is near the view, may need a code-behind
UserControls, lookless Controls (using Styles)
and some view-specific features
^ is perhaps useful for you guys. No more custom controls.
If validation should be in the view is another discussion :)
José Manuel Nieto
@SuperJMN
Jun 19 2015 10:47 UTC
Hahaha
Johan Larsson
@JohanLarsson
Jun 19 2015 10:47 UTC
I wish they had made wpf open source long ago.
Someone said 'WPF is great ideas poorly implemented' I partlially agree.
José Manuel Nieto
@SuperJMN
Jun 19 2015 10:48 UTC
I partially agree :)
Johan Larsson
@JohanLarsson
Jun 19 2015 10:49 UTC
esl, np
I can write dumb things
José Manuel Nieto
@SuperJMN
Jun 19 2015 10:49 UTC
https://github.com/JohanLarsson/Gu.Wpf.Validation
Very interesting, but it drives us to the debate of view-based validation
Steven Kirk
@grokys
Jun 19 2015 10:49 UTC
i think removing codebehind is a worthy ambition, but so many times on SO answers i've seen 2 lines of codebehind replaced by 150 lines of behaviour
i'm not into that
José Manuel Nieto
@SuperJMN
Jun 19 2015 10:50 UTC
is validation always a business thing? I think it is 90% of times :P
Steven Kirk
@grokys
Jun 19 2015 10:50 UTC
yeah, we need to work out a vaidation story for perspex
validation is a definite weakness in WPF
José Manuel Nieto
@SuperJMN
Jun 19 2015 10:50 UTC
@grokys that should be nice!
Johan Larsson
@JohanLarsson
Jun 19 2015 10:50 UTC
Nice thing with the attached props is that they validate as you type. Then the binding can be on lost focus
José Manuel Nieto
@SuperJMN
Jun 19 2015 10:50 UTC
is VERY weak
Johan Larsson
@JohanLarsson
Jun 19 2015 10:51 UTC
very stringy
José Manuel Nieto
@SuperJMN
Jun 19 2015 10:51 UTC
but not because XAML/WPF doesn't have the power
it's because they didn't made an effort big enough to it
I miss a lot of things, like a binding that validates on Enter
and a wise handling of multitasking
Johan Larsson
@JohanLarsson
Jun 19 2015 10:53 UTC
on pressing the enter key?
José Manuel Nieto
@SuperJMN
Jun 19 2015 10:53 UTC
that is horrible as soon as you try to mix viewmodels and tasks
yes :)
Johan Larsson
@JohanLarsson
Jun 19 2015 10:54 UTC
That could easily be added to the attached props
José Manuel Nieto
@SuperJMN
Jun 19 2015 10:55 UTC
yes, but what I'm referring to is that most of things with WPF/XAML are so un-official that it discourages people to use it
Johan Larsson
@JohanLarsson
Jun 19 2015 10:55 UTC
Would be nice if WPF did generics
Virgile Bello
@xen2
Jun 19 2015 10:55 UTC
just discovered this project, seems exciting!
Johan Larsson
@JohanLarsson
Jun 19 2015 10:55 UTC
object everywhere makes me sad
José Manuel Nieto
@SuperJMN
Jun 19 2015 10:56 UTC
welcome @xen2. It is!!
@grokys is the captain of the ship, the workers and the ship
I'm the guy that works on XAML support for it
some people here have also contributed with something!
if you want to involve, just run the code and enjoy :D you'll be hooked
@JohanLarsson It would be a good addition. I always missed it in the past.
Johan Larsson
@JohanLarsson
Jun 19 2015 10:59 UTC
support for generics?
José Manuel Nieto
@SuperJMN
Jun 19 2015 11:00 UTC
yes
Virgile Bello
@xen2
Jun 19 2015 11:07 UTC
@SuperJMN thanks for the intro!
Johan Larsson
@JohanLarsson
Jun 19 2015 11:08 UTC
what would make sense as syntax List(int)?
<> would probably make parisng harder
Benlitz
@Benlitz
Jun 19 2015 11:12 UTC
xml doc use {T} but it might be annoying with markup extensions
(hi, by the way)
Steven Kirk
@grokys
Jun 19 2015 11:13 UTC
hi @xen2 @Benlitz
hi @JohanLarsson !
new people!
yes, i miss generics support in xaml
there's been a couple of times it'd have been useful
Johan Larsson
@JohanLarsson
Jun 19 2015 11:42 UTC
Is there a way to tell what type a binding produces?
The converted type if there is a converter
Steven Kirk
@grokys
Jun 19 2015 11:43 UTC
@JohanLarsson are you talking about XAML or Perspex?
Johan Larsson
@JohanLarsson
Jun 19 2015 11:44 UTC
general wpf q:)
Steven Kirk
@grokys
Jun 19 2015 11:45 UTC
i don't think so
Johan Larsson
@JohanLarsson
Jun 19 2015 11:45 UTC
does Perspex have a nice solution for it?
Steven Kirk
@grokys
Jun 19 2015 11:45 UTC
you can look at the dependency property that it's bound to though
perspex's binding system is completely different
it uses IObservables
Johan Larsson
@JohanLarsson
Jun 19 2015 11:45 UTC
ah, nice
Have you seen Reed Copsey's work on wpf for F#?
Steven Kirk
@grokys
Jun 19 2015 11:46 UTC
also PerspexProperties are typed, e.g. PerspexProperty<double>
no, i've not
Steven Kirk
@grokys
Jun 19 2015 11:58 UTC
@JohanLarsson I'm afraid that means nothing to me! I don't really know any F#
is there an explanation anywhere?
Johan Larsson
@JohanLarsson
Jun 19 2015 11:59 UTC
I don't speak F# either
I can invite him here some time.
I know he did some work on validation.
Steven Kirk
@grokys
Jun 19 2015 12:00 UTC
i don't even know what an F# module is
Johan Larsson
@JohanLarsson
Jun 19 2015 12:00 UTC
I wish ms would drop VB and make F# top priority, the language looks so nice.
Editor support etc not so nice.
Steven Kirk
@grokys
Jun 19 2015 12:01 UTC
yeah, i keep meaning to look into it
VB sux
Johan Larsson
@JohanLarsson
Jun 19 2015 12:01 UTC
Yeah, and having C# and VB with 98% overlap just costs money.
F# brings great stuff.
bigger difference in verbosity F# vs C# than C# vs VB I think.
Steven Kirk
@grokys
Jun 19 2015 12:03 UTC
yep, the terseness is probably what interests me most in F# !
as long as it doesn't get unreadable like the perl i did in 1993 ;)
Johan Larsson
@JohanLarsson
Jun 19 2015 12:03 UTC
default immutable, structural equality for free is nice
Steven Kirk
@grokys
Jun 19 2015 12:04 UTC
yeah, i've been trying to imagine how immutability might work in a UI framework
i can't ;)
Johan Larsson
@JohanLarsson
Jun 19 2015 12:05 UTC
me neither, maybe immutablitiy is a poor fit for viewmodels.
np to have mutable stuff in F#, just that the default is immutable which is nice
Steven Kirk
@grokys
Jun 19 2015 12:05 UTC
yeah, course
it's just the main slowness in perspex at the moment is in layout
if things were immutable that could be done in the b/g
at least partially immutable
Johan Larsson
@JohanLarsson
Jun 19 2015 12:22 UTC
yay, solved the binding type issue.
José Manuel Nieto
@SuperJMN
Jun 19 2015 13:56 UTC
F# sounds nice!
José Manuel Nieto
@SuperJMN
Jun 19 2015 14:30 UTC
Has somebody tried OmniXAML apart from @grokys ?
Johan Larsson
@JohanLarsson
Jun 19 2015 14:36 UTC
not me, I have no x-plat needs at the moment
José Manuel Nieto
@SuperJMN
Jun 19 2015 14:37 UTC
pure pragmatism!
:)
Johan Larsson
@JohanLarsson
Jun 19 2015 14:39 UTC
only heard of it today also :)
José Manuel Nieto
@SuperJMN
Jun 19 2015 14:46 UTC
haha, OK! I hope you could try it and give some feedback
thanks in advance!
Johan Larsson
@JohanLarsson
Jun 19 2015 14:50 UTC
Is there a wiki on how to get started?
Steven Kirk
@grokys
Jun 19 2015 14:51 UTC
started with Perspex or with OmniXaml?
Johan Larsson
@JohanLarsson
Jun 19 2015 14:52 UTC
either or both :)
Steven Kirk
@grokys
Jun 19 2015 14:52 UTC
for perspex there's a little bit of info at https://github.com/grokys/Perspex/tree/master/Docs
in particular the intro document
there's a few blog posts at http://grokys.github.io/
but mainly there's here ;)
Johan Larsson
@JohanLarsson
Jun 19 2015 14:53 UTC
nice
Steven Kirk
@grokys
Jun 19 2015 14:54 UTC
it's still early days, so not documented as well as it could be
the test app in the repos can also be useful, though it's a little hackily written atm as stuf gets bolted on and off as needed
and the Perspex.DevTools project shows MVVM with ReactiveUI
José Manuel Nieto
@SuperJMN
Jun 19 2015 14:55 UTC
@JohanLarsson Trying OmniXAML? https://github.com/SuperJMN/OmniXAML/wiki/Using-OmniXAML-for-WPF I hope you can validate the steps! Thanks :D
Johan Larsson
@JohanLarsson
Jun 19 2015 14:55 UTC
gf booked me for a party tonight, fail, must afk soon.
Steven Kirk
@grokys
Jun 19 2015 14:56 UTC
have a good one!
Johan Larsson
@JohanLarsson
Jun 19 2015 14:58 UTC
@SuperJMN I pushed updates fixing a couple of issues.
José Manuel Nieto
@SuperJMN
Jun 19 2015 14:58 UTC
wow! where are them?
Johan Larsson
@JohanLarsson
Jun 19 2015 14:59 UTC
to the validation thing :)
in case you were interested
José Manuel Nieto
@SuperJMN
Jun 19 2015 15:00 UTC
ahh! you mean to your project?
I'm following it
to take a look!
Kai Eichinger
@cH40z-Lord
Jun 19 2015 16:24 UTC

https://github.com/SuperJMN/OmniXAML/wiki/Using-OmniXAML-for-WPF

regarding

mainWindow = (Window) xamlLoader.Load(stream);

why is there no generic overload? :)

José Manuel Nieto
@SuperJMN
Jun 19 2015 17:29 UTC
@cH40z-Lord Haha, OK. But I thought that, as XAML is inherently un-typed, it would offer no advantages
it would look like this:
mainWindow = xamlLoader.Load<Window>(stream);
it doesn't save you a single keystroke, nor will it offer compiler type safety
Kai Eichinger
@cH40z-Lord
Jun 19 2015 17:36 UTC
isn't one goal of Perspex (and I guess OmniXAML's too?) to get rid of design decisions like that and create more modern APIs? I personally prefer (optional) generic overloads anytime over having to cast manually to improve readability
or is the sole goal of OmniXAML to become 100% compatible with WPF?
José Manuel Nieto
@SuperJMN
Jun 19 2015 17:39 UTC
haha, nice point
100% compatibility is not even desirable, I think
but at least, the key points :)
Kai Eichinger
@cH40z-Lord
Jun 19 2015 17:40 UTC
:P :P
well, I've got it patched in (wasn't really that much). if you wish I can file a PR
José Manuel Nieto
@SuperJMN
Jun 19 2015 17:41 UTC
I'm trying to keep everything as simple as I can
Kai Eichinger
@cH40z-Lord
Jun 19 2015 17:41 UTC
btw what about that TestApplication? VS is complaining that the MainWindow class isn't implementing all necessary methods
José Manuel Nieto
@SuperJMN
Jun 19 2015 17:41 UTC
argh!
can you post the exact message?
@cH40z-Lord OK! but I'm not sure about that. What about creating just an adapter to the loader and offer that extra method?
Kai Eichinger
@cH40z-Lord
Jun 19 2015 17:43 UTC
Severity    Code    Description    Project    File    Line
Error    CS0103    The name 'InitializeComponent' does not exist in the current context    TestApplication    F:\GitHub\OmniXAML\OmniXaml\TestApplication\MainWindow.xaml.cs    12
if I hover the Window class it says that this file is missing the following implementations:
        /// <summary>
        /// Attaches events and names to compiled content. 
        /// </summary>
        /// <param name="connectionId">An identifier token to distinguish calls.</param><param name="target">The target to connect events and names to.</param>
        public void Connect(int connectionId, object target)
        {
            throw new System.NotImplementedException();
        }

        /// <summary>
        /// Loads the compiled page of a component.
        /// </summary>
        public void InitializeComponent()
        {
            throw new System.NotImplementedException();
        }
José Manuel Nieto
@SuperJMN
Jun 19 2015 17:44 UTC
O_O
surprising!
Kai Eichinger
@cH40z-Lord
Jun 19 2015 17:44 UTC
:P
José Manuel Nieto
@SuperJMN
Jun 19 2015 17:44 UTC
is it the main branch?
Kai Eichinger
@cH40z-Lord
Jun 19 2015 17:45 UTC
yeah, master branch
José Manuel Nieto
@SuperJMN
Jun 19 2015 17:45 UTC
and.. the latest version?!
I'm about to take a look to that :P
Kai Eichinger
@cH40z-Lord
Jun 19 2015 17:45 UTC
just checked it out via GitHub Extensions for VS, implemented the two methods, hit build solution which also restored all packages automatically and there we go :P
José Manuel Nieto
@SuperJMN
Jun 19 2015 17:46 UTC
that IS strange!
I'm going to delete my working copy
and clone it again
Kai Eichinger
@cH40z-Lord
Jun 19 2015 17:47 UTC
before you remove your working copy and lose any changes, I'd check it out in a separate folder and go on from there
José Manuel Nieto
@SuperJMN
Jun 19 2015 17:48 UTC
haha, that's is what I'm doing right now
Kai Eichinger
@cH40z-Lord
Jun 19 2015 17:48 UTC
:)
José Manuel Nieto
@SuperJMN
Jun 19 2015 17:48 UTC
haha
the same error is showing!
what the...!
Kai Eichinger
@cH40z-Lord
Jun 19 2015 17:51 UTC
is it possible that it's related to the build action or so? (I've read something like that above)
José Manuel Nieto
@SuperJMN
Jun 19 2015 17:51 UTC
I'm looking for something like that, but it looks OK
Kai Eichinger
@cH40z-Lord
Jun 19 2015 17:52 UTC
weird
José Manuel Nieto
@SuperJMN
Jun 19 2015 17:57 UTC
did you have any problem with Extended.Wpf.Toolkit when building?
Kai Eichinger
@cH40z-Lord
Jun 19 2015 17:58 UTC
yeah, it's complaining about a PropertyGrid
Severity    Code    Description    Project    File    Line
Error        The tag 'PropertyGrid' does not exist in XML namespace 'http://schemas.xceed.com/wpf/xaml/toolkit'. Line 110 Position 18.    TestApplication    F:\GitHub\OmniXAML\OmniXaml\TestApplication\MainWindow.xaml    110
José Manuel Nieto
@SuperJMN
Jun 19 2015 17:58 UTC
Aha... damn it
there seems to be a problem with that package
it doesn't restore OK
Kai Eichinger
@cH40z-Lord
Jun 19 2015 17:59 UTC
hm hm hm
José Manuel Nieto
@SuperJMN
Jun 19 2015 17:59 UTC
I uninstalled it, reinstalled it and the problem with MainWindow disappeared
I think I've fixed the problem
I'm about to commit the fix
Kai Eichinger
@cH40z-Lord
Jun 19 2015 18:01 UTC
:thumbsup:
José Manuel Nieto
@SuperJMN
Jun 19 2015 18:01 UTC
OK, done
I'll check again
that NuGet package has broken me uncountable times
I don't know why the references to the assemblies are usually broken
sometimes, they point to \packages\Extended.Wpf.Toolkit.2.4
and sometimes, they point to packages\Extended.Wpf.Toolkit.2.4.0
(notice the final ".0"?)
Kai Eichinger
@cH40z-Lord
Jun 19 2015 18:03 UTC
yeah
what version of VS are you using?
José Manuel Nieto
@SuperJMN
Jun 19 2015 18:03 UTC
I hope it's fixed now
VS 2015 RC
Kai Eichinger
@cH40z-Lord
Jun 19 2015 18:03 UTC
same here, hm. is it possible that you initially committed this project with VS2013 which may have done it differently?
or maybe it was just a specific version of the NuGet extension that broke it
José Manuel Nieto
@SuperJMN
Jun 19 2015 18:04 UTC
I think it was the latter
it was a nightmare
I had a CI server that was totally unable to restore NuGet Packages
due to that
Kai Eichinger
@cH40z-Lord
Jun 19 2015 18:05 UTC
o_O crazy
José Manuel Nieto
@SuperJMN
Jun 19 2015 18:05 UTC
I would like to have a CI server for OmniXAML
to avoid problems like that
Kai Eichinger
@cH40z-Lord
Jun 19 2015 18:05 UTC
what about appveyor? :)
José Manuel Nieto
@SuperJMN
Jun 19 2015 18:05 UTC
but I don't know how to do it
Kai Eichinger
@cH40z-Lord
Jun 19 2015 18:05 UTC
or TeamCity
José Manuel Nieto
@SuperJMN
Jun 19 2015 18:05 UTC
AppVeyor?
is that free?
Kai Eichinger
@cH40z-Lord
Jun 19 2015 18:06 UTC
yeah, it's a public CI server that offers builds on Windows
afaik it is free for OSS projects
José Manuel Nieto
@SuperJMN
Jun 19 2015 18:06 UTC
cool!
I can set up an account :)
Kai Eichinger
@cH40z-Lord
Jun 19 2015 18:07 UTC
=)
there's also an alternative to the two but I can't remember what its name was lol
José Manuel Nieto
@SuperJMN
Jun 19 2015 18:10 UTC
whoops! it seems it doesn't have .NET Framewor 4.6 installed :P
Kai Eichinger
@cH40z-Lord
Jun 19 2015 18:10 UTC
I see it countless times on GitHub but now when I'd need it I can't remember it x_X
oh? do you already require it? :P
José Manuel Nieto
@SuperJMN
Jun 19 2015 18:10 UTC
yes!
C# 6.0 all the way!
well, Appveyor failed compiling
Kai Eichinger
@cH40z-Lord
Jun 19 2015 18:11 UTC
the .NET version is not related to the C# version :)
José Manuel Nieto
@SuperJMN
Jun 19 2015 18:12 UTC
haha, I know, but I'm targeting 4.6 in some project, I think
Kai Eichinger
@cH40z-Lord
Jun 19 2015 18:12 UTC
alright :)
José Manuel Nieto
@SuperJMN
Jun 19 2015 18:13 UTC
Sin título.png
sniff :worried:
Kai Eichinger
@cH40z-Lord
Jun 19 2015 18:14 UTC
hold on, I've read a blog post about how to use C# 6 on AppVeyor
José Manuel Nieto
@SuperJMN
Jun 19 2015 18:14 UTC
OK! thanks!
in the meanwhile I'm testing the fix
Kai Eichinger
@cH40z-Lord
Jun 19 2015 18:14 UTC
see that "Build Engine v12...."? that should be v14
José Manuel Nieto
@SuperJMN
Jun 19 2015 18:16 UTC
OK! switching!
it's compiling
Kai Eichinger
@cH40z-Lord
Jun 19 2015 18:17 UTC
yay
José Manuel Nieto
@SuperJMN
Jun 19 2015 18:17 UTC
I hope now it's successful
it's taking a lot of time!
and it doesn't show any log now
:S
Kai Eichinger
@cH40z-Lord
Jun 19 2015 18:20 UTC
maybe when it's done
José Manuel Nieto
@SuperJMN
Jun 19 2015 18:21 UTC
if this works, the only thing it'll left not automated will be NuGet packages
:)
OK, it says it's "Queued"
:D :D
btw if you need a private (or just a nightly) nuget feed --> https://www.myget.org/opensource
José Manuel Nieto
@SuperJMN
Jun 19 2015 18:23 UTC
thanks!
I have an account in myget
:)
this is super interesting!
Kai Eichinger
@cH40z-Lord
Jun 19 2015 18:24 UTC
:)
José Manuel Nieto
@SuperJMN
Jun 19 2015 18:24 UTC
I have 2 NuGet nuspec files that should be generated
OmniXaml
and OmniXaml.Wpf
I don't know it that is a good idea
both packages come from the same solution
Kai Eichinger
@cH40z-Lord
Jun 19 2015 18:25 UTC
how do they differ?
José Manuel Nieto
@SuperJMN
Jun 19 2015 18:25 UTC
the package id
the version
and the assemblies
Kai Eichinger
@cH40z-Lord
Jun 19 2015 18:25 UTC
and that's it?
José Manuel Nieto
@SuperJMN
Jun 19 2015 18:25 UTC
yes
Kai Eichinger
@cH40z-Lord
Jun 19 2015 18:26 UTC
well, then it's a bad idea :/
José Manuel Nieto
@SuperJMN
Jun 19 2015 18:26 UTC
the WPF package is thought to be independent
you can take a look to them if you want
Kai Eichinger
@cH40z-Lord
Jun 19 2015 18:27 UTC
hm okay, one requires framework assemblies. then it is fine with me
Kai Eichinger
@cH40z-Lord
Jun 19 2015 19:40 UTC
screenshot-ci.appveyor.com 2015-06-19 21-39-05.png
woop woop!
Build status
José Manuel Nieto
@SuperJMN
Jun 19 2015 20:51 UTC
it's soooo good!
next step, NuGet packages autogenerated and unploaded to nuget.org
Johan Larsson
@JohanLarsson
Jun 19 2015 21:07 UTC
@Super have you created packages before?
José Manuel Nieto
@SuperJMN
Jun 19 2015 21:12 UTC
yes, but I'm not an expert
Johan Larsson
@JohanLarsson
Jun 19 2015 21:13 UTC
I can write a PR for you they way I do them
link to the repo?
Thank you!
Johan Larsson
@JohanLarsson
Jun 19 2015 22:12 UTC
@SuperJMN one problem, I'm on 4.5 looking at a massive diff
Should I revert?
José Manuel Nieto
@SuperJMN
Jun 19 2015 22:13 UTC
There are 2 different
Johan Larsson
@JohanLarsson
Jun 19 2015 22:13 UTC
solutions?
José Manuel Nieto
@SuperJMN
Jun 19 2015 22:13 UTC
Packages
Johan Larsson
@JohanLarsson
Jun 19 2015 22:15 UTC
but when I opened it in 4.5 VS or R# touched every file in the project it seems.
lots of noise
José Manuel Nieto
@SuperJMN
Jun 19 2015 22:15 UTC
sorry, I was writing on my mobile phone and it was almost impossible!
I mean, there are 2 different packages: OmniXaml and OmniXaml.Wpf
Johan Larsson
@JohanLarsson
Jun 19 2015 22:16 UTC
I think I'm reverting
José Manuel Nieto
@SuperJMN
Jun 19 2015 22:16 UTC
please, take a look at them. They are the latests nuspec packages I created
the reference assemblies that are generated from the very same .sln file
(OmniXaml.sln)
@SuperJMN ^ is how I write them, you don't want net45
I usually include .pdbs
I don't have version number in the filename
    <id>$id$</id>
    <version>$version$</version>
    <title>$id$</title>
    <authors>$author$</authors>
    <owners>$author$</owners>
reads version from the assemblyproperties
I handedited so can be mistakes :)
Johan Larsson
@JohanLarsson
Jun 19 2015 22:28 UTC
could not build so could not test
José Manuel Nieto
@SuperJMN
Jun 19 2015 23:31 UTC
Oh :( Is it because it doesn't compile?