在TFS服务器中配置持续集成时出现此错误,但已找到答案.也许这会有助于其他人:
The imported project "C:\Program Files (x86)\
MSBuild\Microsoft\VisualStudio\v10.0\WebApplications\
Microsoft.WebApplications.targets" was not found.
Run Code Online (Sandbox Code Playgroud) 数据:
var data = [
{
"id": 1,
"level": "1",
"text": "Sammy",
"type": "Item",
"items": [
{
"id": 11,
"level": "2",
"text": "Table",
"type": "Item",
"items": [
{
"id": 111,
"level": "3",
"text": "Dog",
"type": "Item",
"items": null
},
{
"id": 112,
"level": "3",
"text": "Cat",
"type": "Item",
"items": null
}
]
},
{
"id": 12,
"level": "2",
"text": "Chair",
"type": "Item",
"items": [
{
"id": 121,
"level": "3",
"text": "Dog",
"type": "Item",
"items": null
},
{
"id": 122, …Run Code Online (Sandbox Code Playgroud) 我创建了Azure容器并设置为Private.必须将权限设置为"私有",因为该内容仅对登录用户可见.但是,我打算在标签中使用blob.当Container设置为Private时,这是不可能的.有没有解决的办法?或者有其他人遇到同样的问题?
我从CodePlex/Code Project下载的所有代码示例(PhluffyPhotos,MyPictures)总是将容器设置为Public(Container/Blob).
谢谢!
零件:
@Component({
selector: 'app-test',
templateUrl: './test.component.html'
})
export class TestComponent implements OnInit {
useCase: string;
constructor(
private route: ActivatedRoute,
) {}
ngOnInit() {
this.route.queryParams.subscribe(p => {
if (p) {
this.useCase = p.u;
}
});
}
}
Run Code Online (Sandbox Code Playgroud)
测试规格
describe('TestComponent', () => {
let component: TestComponent;
let fixture: ComponentFixture<TestComponent>;
beforeEach(async(() => {
TestBed.configureTestingModule({
imports: [
AppModule
],
providers: [
{ provide: ActivatedRoute, useValue: ??? }
]
})
.compileComponents();
}));
beforeEach(() => {
fixture = TestBed.createComponent(TestComponent);
component = fixture.componentInstance;
});
it('should create', () …Run Code Online (Sandbox Code Playgroud) 我正在尝试使用来在Dapper中设置事务隔离级别SqlBuilder,但似乎没有用。
var builder = new SqlBuilder();
var sqlStatement = builder.AddTemplate(@"
SET TRANSACTION ISOLATION LEVEL READ UNCOMMITTED
SELECT * FROM Users
SET TRANSACTION ISOLATION LEVEL READ COMMITTED");
conn.Query<User>(sqlStatement.RawSql);
Run Code Online (Sandbox Code Playgroud)
但这有效:
conn.Execute("SET TRANSACTION ISOLATION LEVEL READ UNCOMMITTED");
var result = conn.Query<User>(sqlStatement);
conn.Execute("SET TRANSACTION ISOLATION LEVEL READ COMMITTED");
Run Code Online (Sandbox Code Playgroud)
我想这可能是因为使用SqlBuilderDapper构建了动态SQL并使用sp_executesql存储过程执行了。
为了证明我的假设,我尝试了以下SQL语句:
exec sp_executesql N'SET TRANSACTION ISOLATION LEVEL READ UNCOMMITTED'
Run Code Online (Sandbox Code Playgroud)
该语句之后,我查询sys.dm_exec_sessions检查我的连接,它仍然显示ReadCommitted数据库中的默认隔离级别。
有什么办法可以SET在单独的地方设置交易级别(或任何其他语句).Execute?或者,也许是一种特殊的使用SET语句的方式sp_executesql?
我有以下界面及其实现
public class DummyProxy : IDummyProxy
{
public string SessionID { get; set; }
public DummyProxy(string sessionId)
{
SessionId = sessionId;
}
}
public interface IDummyProxy
{
}
Run Code Online (Sandbox Code Playgroud)
然后我有另一个类来获取会话ID
public class DummySession
{
public string GetSessionId()
{
Random random = new Random();
return random.Next(0, 100).ToString();
}
}
Run Code Online (Sandbox Code Playgroud)
现在,在我的Unity容器中,每次容器尝试解析IDummyProxy时,我都想向DummyProxy注入'session id'.但是这个'session id'必须从DummySession类生成.
container.RegisterType<IDummyProxy, DummyProxy>(
new InjectionConstructor(new DummySession().GetSessionId()));
Run Code Online (Sandbox Code Playgroud)
这甚至可能吗?
首先,OData响应的标准规范如下:
{
"d" : {
"results": [
{
"__metadata": {
"uri": "http://demos/Orders(10248)",
"type": "SampleModel.Order"
},
"ProductId": 10248,
"Name": "Vgnon"
}
],
"__count": "1"
}
}
Run Code Online (Sandbox Code Playgroud)
但是,在Web API(使用EntitySetController)中,OData响应如下所示:
{
"odata.metadata":"http://localhost:43111/api/$metadata#Products",
"odata.count":"1",
"value":
[
{
"ProductId":2,
"CreatedDate":"2013-06-10T23:53:26",
"CreatedBy":0,"Name":"Camera"
}
]
}
Run Code Online (Sandbox Code Playgroud)
注意两个响应中的计数.Web API遵循OData标准规范吗?
此外,正如这个SO问题所指出的:Web API OData Inlinecount不工作 答案说:
开箱即用$ inlinecount仅在您发回OData响应时有效.
这是否意味着在Web API中(使用EntitySetController或ODataController)我们可以返回OData响应和非OData响应?或者我应该说,标准OData响应和非标准OData响应?
angular ×1
angular-test ×1
asp.net-mvc ×1
azure ×1
c# ×1
dapper ×1
jasmine ×1
javascript ×1
lodash ×1
odata ×1
recursion ×1
sql ×1
sql-server ×1
tfs ×1
unit-testing ×1